ci: add fallback for helm install when get.helm.sh is down #21268
Conversation
Add a fallback step that installs helm via apt from Buildkite's repository if the primary azure/setup-helm action fails. This makes CI resilient to get.helm.sh outages while preserving the caching benefits of the action when it works. The fallback uses GPG-signed packages from the official Helm apt repository hosted by Buildkite, as recommended by the Helm docs. Fixes: coder/internal#1109
jdomeracki-coder
left a comment
There was a problem hiding this comment.
Seems reasonable
johnstcn
left a comment
There was a problem hiding this comment.
Do we anticipate the fallback to be more reliable than get.helm.sh? If so, should we just switch to that method entirely?
It might also be a good idea to run helm version or somehow specify the version of Helm we use to avoid flakes.
|
@johnstcn Neither source is inherently more reliable - get.helm.sh is official Helm infrastructure, while Buildkite's apt repo is community-maintained but recommended by Helm docs. The fallback approach provides redundancy - if either is down, the other is available. Switching entirely to apt would trade one single point of failure for another. Added a helm version --short step to verify the correct version was installed. |
Add a fallback step that installs helm via apt from Buildkite's repository if the primary
azure/setup-helmaction fails. This makes CI resilient toget.helm.shoutages while preserving the caching benefits of the action when it works.Changes
azure/setup-helmwithcontinue-on-error: trueThe fallback uses GPG-signed packages from the official Helm apt repository hosted by Buildkite.
Background
On Oct 29, 2025,
get.helm.shexperienced an outage that broke CI. A workaround was applied (#20552) but later reverted. This PR makes the workaround automatic - it only kicks in when needed.Fixes: coder/internal#1109