-
Notifications
You must be signed in to change notification settings - Fork 0
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
add Secret resource #32
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
helm/alloy/templates/secret.yaml
Outdated
{{- if .Values.alloy.alloy.secret.content }} | ||
{{- .Values.alloy.alloy.secret.content | nindent 2 }} | ||
{{- else }} | ||
{{- .Files.Get "config/example.secret" | nindent 2 }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer that you require the .Values.alloy.alloy.secret.content
to not be empty than provide an incorrect config though
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a good point so I did move the secret example into helm/alloy/examples/mimir-rules
I assume the secrets needs to be mounted via env variables? Could you add an example explaining how here? |
Also, please open the PR upstream as well to make sure this is supported in the long run |
Just did that in
Will do |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<3
Submitted a PR upstream to add support for the Secret resource grafana/alloy#1502 Also updated this PR to align with the proposition made upstream. |
Towards: giantswarm/roadmap#3522
This PR adds a secret resource into the Alloy helm chart to allow passing secret configuration via helm values.