Skip to content
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

Merged
merged 7 commits into from
Aug 20, 2024
Merged

add Secret resource #32

merged 7 commits into from
Aug 20, 2024

Conversation

TheoBrigitte
Copy link
Member

Towards: giantswarm/roadmap#3522

This PR adds a secret resource into the Alloy helm chart to allow passing secret configuration via helm values.

@TheoBrigitte TheoBrigitte self-assigned this Aug 16, 2024
@TheoBrigitte TheoBrigitte requested a review from a team as a code owner August 16, 2024 10:09
@TheoBrigitte TheoBrigitte changed the title Secret add Secret resource Aug 16, 2024
Copy link
Contributor

@QuantumEnigmaa QuantumEnigmaa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

{{- if .Values.alloy.alloy.secret.content }}
{{- .Values.alloy.alloy.secret.content | nindent 2 }}
{{- else }}
{{- .Files.Get "config/example.secret" | nindent 2 }}
Copy link
Contributor

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

Copy link
Member Author

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

@QuentinBisson
Copy link
Contributor

I assume the secrets needs to be mounted via env variables? Could you add an example explaining how here?

@QuentinBisson
Copy link
Contributor

Also, please open the PR upstream as well to make sure this is supported in the long run

@TheoBrigitte
Copy link
Member Author

I assume the secrets needs to be mounted via env variables? Could you add an example explaining how here?

Just did that in helm/alloy/examples/mimir-rules

Also, please open the PR upstream as well to make sure this is supported in the long run

Will do

Copy link
Contributor

@QuentinBisson QuentinBisson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

<3

@TheoBrigitte
Copy link
Member Author

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.

@TheoBrigitte TheoBrigitte merged commit 3e8d33b into main Aug 20, 2024
4 checks passed
@TheoBrigitte TheoBrigitte deleted the secret branch August 20, 2024 12:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants