ork e2e — Orkestra

Run declarative end-to-end tests against a real cluster.

ork e2e -f e2e.yaml

ork e2e is the complement to ork simulate — it runs against a real kind cluster, applying the full operator lifecycle and verifying that resources reach the expected state. The same command runs locally and in CI.

Flags

Flag	Short	Default	Description
`--file`	`-f`	`e2e.yaml`	Path to the E2E spec file
`--keep-cluster`		`false`	Keep the kind cluster after the test completes
`--cluster`		(create new)	Use an existing kubectl context instead of creating a cluster

What it does

Creates a kind cluster (or reuses --cluster context)
Installs operator dependencies (CRDs, namespaces, Helm charts)
Applies the CRD and operator bundle
Starts the Orkestra runtime
Applies the CR
Polls each spec.expect block until all resources reach the expected state or the timeout expires
Cleans up the cluster (unless --keep-cluster)

e2e.yaml spec

apiVersion: orkestra.io/v1alpha1
kind: E2E
metadata:
  name: hello-website
  description: Verifies the website operator creates a deployment and service
spec:
  katalog: katalog.yaml
  crd: website
  cr: cr.yaml
  expect:
    - name: deployment ready
      after: cr-applied
      timeout: 60s
      resources:
        - kind: Deployment
          name: hello-website-deployment
          namespace: default
          conditions:
            - type: Available
              status: "True"

Examples

# Run e2e tests defined in e2e.yaml
ork e2e -f e2e.yaml

# Keep the cluster for debugging after the test
ork e2e -f e2e.yaml --keep-cluster

# Run against an existing cluster context
ork e2e -f e2e.yaml --cluster my-dev-context

# Validate the e2e spec before running
ork validate -f e2e.yaml