> ## Documentation Index
> Fetch the complete documentation index at: https://docs.macstadium.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Orka component versions by release

> Expected Orka API server, operator, Virtual Kubelet, Orka Engine, and CLI versions for each Orka release, and how to check them on your cluster.

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.

| Command | Output field | Component |
| - | - | - |
| `orka3 version` | `Client Version` | Your local `orka3` CLI |
| `orka3 version` | `API Version` | Orka API server |
| `orka3 version` | `Operator Version` | Orka operator. The Orka webhooks and custom resource definitions (CRDs) ship with the operator and match its version. |
| `orka3 version` | `Upgrade Service Operator Version`, `Upgrade Service Cluster Agent Version` | Orka Upgrade Service. These lines only appear when the Upgrade Service is installed. |
| `orka3 node list -o wide` | `VERSION` | Virtual Kubelet on each node |
| `orka3 node list -o wide` | `RUNTIME` | Orka Engine on each node |

The following output is from a cluster on Orka 3.6.4, with the `Client Version` line omitted:

```
$ orka3 version
API Version: v3.6.3-c8fe8aed
Operator Version: v3.6.4-ba2b3182

$ orka3 node list -o wide
NAME             ...  VERSION           RUNTIME
m2-studio-0101   ...  v3.6.4-108a65f8   orka-engine://3.6.3-c8fe8aed
m4-studio-160    ...  v3.6.4-108a65f8   orka-engine://3.6.3-c8fe8aed
```

Every value matches the 3.6.4 row in the following matrix, so this cluster is on Orka 3.6.4.

<Note>
  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.
</Note>

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.

| Release | API server | Operator | Webhooks | CRDs | Virtual Kubelet | Orka Engine | Orka3 CLI |
| - | - | - | - | - | - | - | - |
| 3.7.0-alpha | 3.7.0-alpha | 3.7.0-alpha | 3.7.0-alpha | 3.7.0-alpha | 3.7.0-alpha | 3.7.0-alpha | 3.7.0-alpha |
| 3.6.4 | 3.6.3\* | 3.6.4 | 3.6.4 | 3.6.4 | 3.6.4 | 3.6.3\* | 3.6.4 |
| 3.6.3 | 3.6.3 | 3.6.3 | 3.6.3 | 3.6.3 | 3.6.3 | 3.6.3 | 3.6.3 |
| 3.6.2 | 3.6.2 | 3.6.2 | 3.6.2 | 3.6.2 | 3.6.2 | 3.6.2 | 3.6.2 |
| 3.6.0 | 3.6.0 | 3.6.0 | 3.6.0 | 3.6.0 | 3.6.0 | 3.6.0 | 3.6.0 or 3.6.1 |
| 3.5.3 | 3.5.0\* | 3.5.3 | 3.5.3 | 3.5.3 | 3.5.2\* | 3.5.2\* | 3.5.2\* |
| 3.5.2 | 3.5.0\* | 3.5.2 | 3.5.2 | 3.5.2 | 3.5.2 | 3.5.2 | 3.5.2 |
| 3.5.1 | 3.5.0\* | 3.5.1 | 3.5.1 | 3.5.1 | 3.5.1 | 3.5.0\* | 3.5.1 |
| 3.5.0 | 3.5.0 | 3.5.0 | 3.5.0 | 3.5.0 | 3.5.0 | 3.5.0 | 3.5.0 |
| 3.4.2 | 3.4.0\* | 3.4.0\* | 3.4.0\* | 3.4.0\* | 3.4.1\* | 3.4.2 | 3.4.0\* |
| 3.4.1 | 3.4.0\* | 3.4.0\* | 3.4.0\* | 3.4.0\* | 3.4.1 | 3.4.0\* | 3.4.0\* |
| 3.4.0 | 3.4.0 | 3.4.0 | 3.4.0 | 3.4.0 | 3.4.0 | 3.4.0 | 3.4.0 |

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](/orka/orka-upgrades-and-release-notes/orka-release-notes#orka-3-7-0-alpha) for details.

<Note>
  **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](/orka/orka-upgrades-and-release-notes/upgrading-orka-anywhere).
</Note>

## Independently versioned components

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

* **Orka Upgrade Service:** introduced in Orka 3.6.0 as version 1.0.0. See [Orka Upgrade Service](/orka/orka-upgrades-and-release-notes/orka-upgrade-service).
* **Orka VM Tools:** runs inside each macOS guest VM. On the 3.6 release line, VM Tools stays at 3.6.0 for every patch release. See [Orka VM Tools](/orka/orka-resources/vm-tools).
* **CI/CD integrations:** plugins such as the GitHub Actions integration release on their own schedule. See [Orka tools, CLI downloads, and CI/CD plugins](/orka/orka-overview/tools-integrations).

## Common questions

<AccordionGroup>
  <Accordion title="We upgraded to 3.6.4, but orka3 version shows API version 3.6.3. Did the upgrade fail?">
    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.
  </Accordion>

  <Accordion title="Our 3.5.2 cluster shows API version 3.5.0. Is that expected?">
    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.
  </Accordion>

  <Accordion title="My orka3 CLI is a different version from my cluster. Is that a problem?">
    Use the CLI version listed for your release in the [component version matrix](#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](/orka/orka-overview/tools-integrations) to download a specific CLI version.
  </Accordion>

  <Accordion title="Some nodes report a different Virtual Kubelet or Orka Engine version from others. Why?">
    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](mailto:support@macstadium.com) with the output of `orka3 node list -o wide`.
  </Accordion>
</AccordionGroup>


## Related topics

- [Orka release notes](/orka/orka-upgrades-and-release-notes/orka-release-notes.md)
- [Orka3 CLI Overview & Configuration](/orka/orka3-cli-reference/orka3-cli-overview-configuration.md)
- [How to upgrade your Orka cluster](/orka/orka-upgrades-and-release-notes/orka-upgrades.md)
- [Run guided Orka cluster upgrades with Upgrade Service](/orka/orka-upgrades-and-release-notes/orka-upgrade-service.md)
- [Cluster Configurations](/orka/orka-resources/cluster-configurations.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.