How to upgrade the versions of the support chart’s dependencies#
The support chart depends on some external helm charts which have their own release cadence.
We also have an extra dependency in cert-manager
managed by the deployer
.
This documentation covers the steps to take to update the version of these dependencies and rolling them out.
Runbook steps#
Trigger the GitHub Action workflow to generate a PR that will bump the versions of the support chart’s dependencies if newer versions are available.
Check for a new
cert-manager
release and bump the value in thedeployer
.cert-manager
is not listed as a dependency of the support chart since it is deployed into it’s own namespace. Instead the code that handles installing it lives in the deployer.You can find the latest available of
cert-manager
by checking the releases page or by running the below command in a terminal.helm search repo jetstack/cert-manager --versions
Update the [section of
deployer
code] that installscert-manager
with the new version, and commit this to the same PR that the workflow opened. You can get a copy of the PR locally by running thisgh
command:gh pr checkout <pr-number>
For any dependencies that will be bumped, check the release notes for mention of any breaking changes we should be aware of.
If you find a breaking change or are unsure of a specific upgrade, you can revert the change in the PR, commit and push it.
Deploy the PR to a test cluster and monitor it.
Choose a test cluster to deploy the PR to and monitor it for 24 hours or so. If the
cluster-autoscaler
dependency is being upgraded, then it’s best to test on an AWS cluster as that dependency is only enabled on AWS deployment.deployer deploy-support $CLUSTER_NAME
If there are no issues with the test cluster, merge the PR to deploy to all clusters.