fix: Use GitLab-hosted repo
And update requirements.lock with helm dep update
. As Helm is removing
the old stable repo.
There is no functional change - we are still using the same 0.7.1 postgresql version.
Technically this repo is deprecated but we are doing this because:
- It's BREAKING because of the helm stable removal
- We provide an example for people who may have previously forked
Merge request reports
Activity
changed milestone to %13.6
added groupconfigure [DEPRECATED] severity1 typebug labels
assigned to @hfyngvason and unassigned @tkuah
@tkuah Will this work without the accompanying
helm repo add
inauto-deploy-image
? Wouldn't most users affected by this repository's old requirements be missing that?That's true, it won't work. The calling code
helm repo add stable-archive https://gitlab-org.gitlab.io/cluster-integration/helm-stable-archive
needs to be added somewhere. But at least that can be added. Without this MR, older GitLab instances are effectively stuck.@tkuah
👍 So then this looks good to me, but since this will take effect immediately, when should we merge? Should we merge immediately, or wait until November 13?
assigned to @tkuah and unassigned @hfyngvason
Setting label(s) ~"devops::configure" sectionops based on ~"group::configure".
added devopsconfigure [DEPRECATED] sectionops labels
Surprisingly, https://kubernetes-charts.storage.googleapis.com/ is still alive
mentioned in commit ab286549