Helm Chart Discussion #262
daun-gatal
started this conversation in
General
Replies: 1 comment 3 replies
|
From my side the secret references are the way to go - I would even say its mandatory as thats where the most of helm chart fails. Not to make it overbloated and biased I htink the properties for secrets should include a value suffixed with auth:
jwt:
secretRef: my-secret-in-k8s
secretKey: key-name-I-used
# ... same for other configurations now for preconfigured SSO in chart - we need to figure out how to tackle that one as we do have predictable naming convention and setup where we can use ENV vars for specific secret values - so that's definitely a case we need to test Once we start rolling out we can do some more tests and I guess things will come up to fix :) |
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi @RafPe lets use discussion about the helm chart. Can share your suggestions here also. Thank you.
cc @abduldjafar
All reactions