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 distributed as an OCI Helm chart and upgraded via Helm. There is no Helm repository to add; you pull the chart directly from the OCI registry.

Reuse your existing values​

clusterToken and apiKey have no defaults in the chart, so you must either pass them again on every upgrade or reuse the values from the current release. The simplest approach is --reuse-values, which keeps the configuration from your last install or upgrade.

Steps​

  1. Check current version:

    helm list -n opsworker-agent

  2. Upgrade the agent from the OCI chart:

    helm upgrade opsworker-agent oci://public.ecr.aws/k1v3l8a8/opsworker-agent \
      -n opsworker-agent --reuse-values

    To move to a specific chart version, add --version <version>. If you prefer to supply configuration explicitly instead of --reuse-values, pass your values file and the required secrets:

    helm upgrade opsworker-agent oci://public.ecr.aws/k1v3l8a8/opsworker-agent \
      -n opsworker-agent -f my-values.yaml \
      --set clusterToken=<token> --set apiKey=<key>

  3. Watch the rollout:

    kubectl rollout status deployment/opsworker-agent -n opsworker-agent

  4. Verify (expect three pods: agent, kubernetes-mcp-server, grafana-mcp):

    kubectl get pods -n opsworker-agent

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-agent

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​