Skip to main content
An Orka cluster is made up of separately versioned components that ship together as a release. A patch release only publishes new builds of the components it changed, so some components keep the version number of an earlier release. Your cluster’s version is the release version, even when orka3 version or orka3 node list -o wide reports an earlier number for some components. For example, a cluster on Orka 3.6.4 runs the API server and Orka Engine at 3.6.3, because neither changed in 3.6.4.

​
Check the component versions on your cluster

Two orka3 commands report component versions. The following table lists which component each field belongs to. The following output is from a cluster on Orka 3.6.4, with the Client Version line omitted:
Every value matches the 3.6.4 row in the following matrix, so this cluster is on Orka 3.6.4.
Compare the version number only. The suffix after the version, such as -c8fe8aed, identifies the build. It can differ between clusters on the same release and doesn’t indicate a different version.On Orka 3.4 clusters the Orka Engine version itself ends in -oc, so RUNTIME reads as orka-engine://3.4.2-oc-<build>. The -oc is part of the version and should match the matrix; only the build suffix after it varies.
To print only your local CLI version without contacting the cluster, run orka3 version --client.

​
Component version matrix

The following table lists the version of each component in each Orka release, starting with Orka 3.4.0. An asterisk (*) marks a component that wasn’t changed in that release and keeps the version from an earlier release. Orka3 CLI 3.6.1 shipped for 3.6.0 clusters without any cluster component changes, so a 3.6.0 cluster works with either CLI version. Orka 3.7.0-alpha is an early-access preview. See the Orka release notes for details.
Orka Anywhere on-premises clusters upgraded to 3.6.4: the ghcr.io/macstadium/orka-ansible-onprem:3.6.4 installer image published before October 1, 2026 deployed the operator, CRDs, and Virtual Kubelet at 3.6.3. If your cluster reports operator 3.6.3 after a 3.6.4 upgrade, re-pull the 3.6.4 installer image and run the upgrade again. See Upgrade a self-managed Orka Anywhere cluster.

​
Independently versioned components

The following components have their own version numbers, which don’t follow the Orka release number:

​
Common questions

No. Orka 3.6.4 didn’t change the API server or Orka Engine, so both stay at 3.6.3. Your cluster is on 3.6.4 when the operator and the Virtual Kubelet on each node report 3.6.4.
Yes. Neither Orka 3.5.1 nor 3.5.2 changed the API server, so it stays at 3.5.0 on every 3.5.x cluster.
Use the CLI version listed for your release in the component version matrix. A newer CLI can include commands your cluster doesn’t support yet. For example, orka3 imagecache remove requires the cluster itself to run Orka 3.6.3 or later, and updating only the CLI isn’t enough. See Orka tools, CLI downloads, and CI/CD plugins to download a specific CLI version.
Each node reports its own Virtual Kubelet and Orka Engine versions. If one node reports an earlier version than the matrix lists for your release, that node’s tooling wasn’t upgraded. Contact MacStadium support with the output of orka3 node list -o wide.