Skip to main content

Upgrade Guide

OpsWorker Cloud​

The OpsWorker SaaS platform is updated automatically. No customer action is needed for cloud-side upgrades. New features and improvements are deployed continuously.

Kubernetes Agent​

The in-cluster agent is upgraded via Helm.

Steps​

  1. Check current version:

    helm list -n opsworker

  2. Update Helm repository:

    helm repo update opsworker

  3. Upgrade the agent:

    helm upgrade opsworker-agent opsworker/opsworker-agent -n opsworker

  4. Watch the rollout:

    kubectl rollout status deployment/opsworker-agent -n opsworker

  5. Verify:

    kubectl get pods -n opsworker

Zero-Downtime Upgrade​

The Helm upgrade performs a rolling update — the new pod starts before the old one terminates, ensuring no gap in agent availability.

Rollback​

If the upgrade causes issues:

helm rollback opsworker-agent -n opsworker

Checking for Updates​

  • Agent version is visible in cluster settings in the OpsWorker portal
  • The portal indicates when a newer agent version is available

Best Practices​

  • Upgrade agents during low-traffic periods
  • Test upgrades on a non-production cluster first
  • Review the changelog for breaking changes before upgrading

Next Steps​