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. Replace <version> with a version number such as 0.3.0:

FileWhat it contains
orka-<version>.tgzThe Helm chart used to install Orka
orka_v<version>_linux_amd64.tar.gzThe CLI for Linux on x86-64
orka_v<version>_linux_arm64.tar.gzThe CLI for Linux on ARM64
orka_v<version>_darwin_amd64.tar.gzThe CLI for macOS on Intel
orka_v<version>_darwin_arm64.tar.gzThe CLI for macOS on Apple silicon
orka_v<version>_windows_amd64.zipThe CLI for Windows on x86-64
orka_v<version>_checksums.txtSHA-256 checksums for the five CLI archives
orka_v<version>_checksums.txt.bundleThe keyless Cosign signature and verification material for the checksum file
candidate.jsonThe version, source commit, image digests, and SHA-256 hashes for the chart and CLI assets
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 SHA-256 hashes for the chart, CLI archives, checksum file, and signature bundle. Use these to inspect a release or pin images. See CLI installation to choose a download and verify it. 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, chart, and CLI archives, 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.