Documentation structure for LLMs (llms.txt)
CircleCI Logo

Update the Kubernetes release agent

23 hours ago
Cloud

Follow the steps on this page to update the CircleCI release agent installed in your Kubernetes cluster.

Refer to the CircleCI Changelog to find out about new release agent versioning, updates, and fixes.

Prerequisites

To update the Kubernetes release agent you need an operational CircleCI environment integrated with your Kubernetes cluster. Refer to the following pages for steps:

If you used the release agent prior to version 1.2.0, you used app and version in place of circleci.com/component-name and circleci.com/version. While app and version are still supported, we recommend migrating to the new labels as soon as possible.

Support for the old labels will be dropped in one of the next releases.

After migrating to the new labels, rolling back to versions that used the old labels will be supported only for deployments and Rollouts managed through Helm.

Upgrading to v1.6.0: Release agent v1.6.0 and Helm chart v1.6.0 introduce managedNamespacesMode (static or dynamic). The default is static, which preserves the existing behavior.

The release agent monitors the exact namespace names in managedNamespaces with no change to RBAC permissions. No action is required when upgrading if you want to keep the existing static behavior.

To opt in to dynamic mode (glob-pattern namespace discovery), re-run helm upgrade with --set managedNamespacesMode=dynamic --set rbac.clusterRoles=true after upgrading. See the Managed Namespaces Mode section for details.

Update steps

  1. Update your local Helm cache:

    helm repo update

  2. Upgrade to the new version:

    helm upgrade --install circleci-release-agent-system release-agent/circleci-release-agent \
--set tokenSecret.token=[YOUR_CCI_INTEGRATION_TOKEN] --create-namespace \
--namespace circleci-release-agent-system \
--set managedNamespaces="{namespace1,namespace2}"

    If the agent was installed with the integration token stored in the Helm release, you can omit --set tokenSecret.token on upgrade. Use --reuse-values when applying a values file that does not include the token. Do not use --reset-values unless you also supply the token again. See Set up the CircleCI Release Agent for details on storing and managing integration tokens.