-
Notifications
You must be signed in to change notification settings - Fork 3.8k
fix(helm): fix imagePullSecrets for statefulset-results-cache #13051
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
+1 |
|
@Haibread hey thanks for your contribution ❤️ sorry for the delay; do you mind resolving the conflicts? if you don't have the time this week, I can fix them, just let me know. |
Should be good to go, let me know if I need to edit anything |
|
This change broke the entire chart? Before we had this in our values.yaml: image:
pullSecrets:
- harbor-infra-run-pull-secret
imagePullSecrets:
- name: harbor-infra-run-pull-secretIt was strange to specify pull secrets twice in two different formats, but worked for all workloads included in the loki helm chart. With this change, we now can just do imagePullSecrets:
- harbor-infra-run-pull-secretwhich is nice and works for the cache statefulsets but breaks loki-gateway, loki-read, loki-backend, and loki-write deployments as they are not automtically adding the |
What this PR does / why we need it:
If you set the
imagePullSecretsvalue, you will encounter an error as helm cannot template the statefulset-results-cache.yaml file :This PR fixes this issue, which appears to be caused by a typo between
$.ctx.Values.imagePullSecretsand$.ctx.Values.image.pullSecretsto match thevalues.yamlfileWhich issue(s) this PR fixes:
Fixes #12632
Special notes for your reviewer:
Checklist
CONTRIBUTING.mdguide (required)featPRs are unlikely to be accepted unless a case can be made for the feature actually being a bug fix to existing behavior.docs/sources/setup/upgrade/_index.mdproduction/helm/loki/Chart.yamland updateproduction/helm/loki/CHANGELOG.mdandproduction/helm/loki/README.md. Example PRdeprecated-config.yamlanddeleted-config.yamlfiles respectively in thetools/deprecated-config-checkerdirectory. Example PR