jwntrs

apiVersion: carto.run/v1alpha1
kind: ClusterSupplyChain
metadata:
  name: supply-chain
spec:
  selector:
    matchLabels:
      workload-type: web

  resources:

jwntrs

apiVersion: carto.run/v1alpha1
kind: ClusterSupplyChain
metadata:
  name: supply-chain
spec:
  resources:
    - name: source-provider
      templateRef:
        kind: ClusterSourceTemplate
        options:

jwntrs

apiVersion: carto.run/v1alpha1
kind: ClusterSupplyChain
metadata:
  name: supply-chain
spec:
  selector:
    matchLabels:
      workload-type: web

jwntrs

apiVersion: carto.run/v1alpha1
kind: ClusterSupplyChain
metadata:
  name: supply-chain
spec:
  selector:
    matchLabels:
      workload-type: web

  snippets:

jwntrs

apiVersion: carto.run/v1alpha1
kind: ClusterSourceSupplyChain
metadata:
  name: gitops-supply-chain
spec:
  selector:
    matchLabels:
      workload-type: web
    matchFields:
    - {key: ".spec.target", operation: In, value: ["gitops"]}

jwntrs

apiVersion: carto.run/v1alpha1
kind: ClusterSupplyChain
metadata:
  name: supply-chain
spec:
  selector:
    matchLabels:
      workload-type: web

  resources:

jwntrs

Duck types

The new app stack architecture relies heavily on the use of duck types throughout the system.

But what if the user wants to user a 3rd party tool that doesn't conform to the duck-type.

Exposing custom status

jwntrs

Overview

The two most important concepts to understand in kontinue are sources, and workflows.

        *unit* -------------------------- *build* ---------------------- *deploy* ------------- *integration*
[src-code, golang-image]     [src-code, builder-base-image]      [src-code, redis-image]         [src-code]

jwntrs

apiVersion: experimental.kontinue.io/v1
kind: Workflow
metadata:
  name: app
spec:
  sources:
    - name: repo
      sourceRefs:
      - name: app
        kind: GitSource

jwntrs

apiVersion: experimental.kontinue.io/v1
kind: Workflow
metadata:
  name: app
spec:
  sources:
    - name: repo
      sourceRefs:
      - name: app
        kind: GitSource