> ## 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.

# Upgrading Orka Anywhere

> Overview of upgrading a self-managed Orka Anywhere cluster, AWS-hosted or on-premises, and where to find the detailed steps for each.

Orka Anywhere is any Orka deployment you run and manage yourself, whether that's AWS-hosted or fully on-premises, as opposed to a MacStadium-managed deployment. Upgrades are self-service: you run the same Ansible-based process you used to stand up your cluster, pointed at the Ansible image tagged for your target release.

There are two parts to every upgrade:

* **Services upgrade:** upgrades the Orka Kubernetes services.
* **Node tooling upgrade:** updates the Virtual Kubelet and Orka Engine on your ARM Mac nodes in place, without replacing the node.

Review the [release notes](/orka/orka-upgrades-and-release-notes/orka-release-notes) for your target version before upgrading.

## AWS-hosted

Fully documented today. See [Upgrading Orka on AWS](/orka/orka-upgrades-and-release-notes/upgrading-orka-on-aws) for the full step-by-step, including node tag verification, SSH and SSM upgrade paths for ARM node tooling, and multi-region guidance.

## On-premises

On-premises upgrades reuse the exact same `ghcr.io/macstadium/orka-ansible-onprem` container and the same `cluster.yml`, `nodes.yml`, and `hosts` files you used to install, from [Orka On-Prem architecture and networking overview](/orka/orka-on-aws-and-on-prem/orka-on-prem-getting-started). The playbooks are idempotent, re-running them re-converges your cluster to the target version rather than requiring a separate upgrade procedure. One thing differs from install:

1. **Use your target version's tag** in place of `<version_tag>` in both `docker run` commands: [Installing the Orka Cluster Services](/orka/orka-on-aws-and-on-prem/orka-on-prem-getting-started#installing-the-orka-cluster-services) for the services upgrade (`ansible-playbook site.yml`), [Setting Up Mac Nodes](/orka/orka-on-aws-and-on-prem/orka-on-prem-getting-started#setting-up-mac-nodes) for the ARM node tooling upgrade (`ansible-playbook configure-arm.yml -i hosts --ask-become-pass`).

You don't normally need to set `osx_node_orka_engine_version` or `osx_node_orka_vk_version` in `nodes.yml` for a routine upgrade. Set them only if MacStadium has given you a specific build to deploy, for example a custom build for your environment.

Node tooling (Virtual Kubelet and Orka Engine) is version-gated rather than blindly replaced: the playbook compares the installed version against the target and only updates on a mismatch, so re-running against nodes already on the target version is a no-op.

<Note>
  This page covers upgrading the Orka services and node tooling via Ansible. If you're separately running the Orka Upgrade Service on an Anywhere cluster and need to migrate it from v1 to v2, a dedicated `kubectl`-only migration script exists for exactly that. Full guidance on the Upgrade Service is being documented separately, in the meantime [contact your MacStadium account team](mailto:support@macstadium.com) for the migration steps.
</Note>

## Hybrid deployments (EKS control plane + on-premises Mac nodes)

If your deployment combines an EKS control plane on AWS with Mac nodes on-premises, upgrade each part using the workflow for where it runs: the AWS guide above for the control plane and AWS-side services, and the on-premises path for your Mac nodes.

## After the upgrade

[Download and install](/orka/orka-overview/tools-integrations) the orka3 CLI version matching your upgraded cluster, if you haven't already.


## Related topics

- [Orka On-Prem architecture and networking overview](/orka/orka-on-aws-and-on-prem/orka-on-prem-getting-started.md)
- [Upgrading Orka on AWS](/orka/orka-upgrades-and-release-notes/upgrading-orka-on-aws.md)
- [Orka Anywhere On-Prem: Troubleshooting VM Deployments](/orka/orka-on-aws-and-on-prem/orka-on-prem-troubleshooting.md)
- [Post-migration tasks after upgrading Orka 2.4.x to 3.0.0](/orka/orka-cluster-migration-from-24-3x/24x-to-300-after-the-migration.md)
- [Orka Upgrade Service](/orka/orka-upgrades-and-release-notes/orka-upgrade-service.md)
