Skip to main content

Release status

Get published versions from GitHub Releases. For a new installation, follow Install Orka.

Release files​

The release workflow publishes these files:

FileWhat it contains
orka-<version>.tgzThe Helm chart used to install Orka
candidate.jsonThe version, source commit, image IDs, and chart checksum
qualification.jsonThe release test run and checksums for its reports
acceptance.jsonResults for installation, restart, agent, publication, and cleanup tests

The chart uses release version tags by default. candidate.json records the exact image digests and chart checksum for inspecting a release or pinning images. The chart is also available from Orka's Helm repository at https://orka-agents.github.io/orka/charts.

Check your installation​

For a Helm release named orka in orka-system, check the chart version, controller image, and CRDs. Use the same cluster connection name as your installation:

export ORKA_CONTEXT='<your-kubeconfig-context>'
helm list --kube-context "${ORKA_CONTEXT}" --namespace orka-system
kubectl --context "${ORKA_CONTEXT}" -n orka-system get deploy orka-controller \
  -o jsonpath='{.spec.template.spec.containers[0].image}{"\n"}'
kubectl --context "${ORKA_CONTEXT}" get crd -o name | grep -c '\.orka\.ai$'

Compare the CRDs with those in your release's chart. Development CRDs are packaged separately. A CRD count alone does not identify the running version because Kubernetes keeps CRDs after an uninstall. Check the chart version and image too.

Build from source​

Follow Build from source for development. This builds your own images; ordinary pushes to main do not publish release images.

Use manifest_staging/charts/orka, which make manifests generates from current source. The root charts/orka and deploy directories are release snapshots and may lag behind the source code.

How a release is published​

  1. A maintainer starts Prepare Release from main and enters the version.
  2. The workflow prepares a release branch, builds the images and chart, and waits for approval to run the release tests.
  3. After the tests pass, a maintainer approves publication. The workflow tags the tested commit and publishes the images, chart, and GitHub Release files.

See Release automation for the maintainer instructions and test details.

Support​

Orka is pre-1.0 and is not yet supported for production use. See Upgrading before updating an installation or planning a backup restore.