Skip to content

Don't manage the k8s secret for prometheus auth from this chart - #121

Merged
jnywong merged 1 commit into
2i2c-org:mainfrom
GeorgianaElena:envFromSecret
Jul 31, 2026
Merged

Don't manage the k8s secret for prometheus auth from this chart#121
jnywong merged 1 commit into
2i2c-org:mainfrom
GeorgianaElena:envFromSecret

Conversation

@GeorgianaElena

@GeorgianaElena GeorgianaElena commented Jul 31, 2026

Copy link
Copy Markdown
Member

Ref 2i2c-org/infrastructure#8851

Currently this chart gets the prometheus username and password via values.yaml, then puts it in a k8s secret and has the deployment consume it.

What happens in practice, in our 2i2c deployments of this chart, is that we end up with two k8s secrets that manage the prometheus creds. One managed by this deployment and one managed by basehub, each needing its own values.yaml setup, which results having two places where we need to maintain this info.

This PR has prometheusAuth.envFromSecret specify the name of the secret where the promethus username and password is and uses that instead. This is similar to how we setup grafana creds

https://github.com/2i2c-org/infrastructure/blob/81b82d1a1646de73074c46e23e864612ebf8497f/helm-charts/support/values.yaml#L359

@GeorgianaElena
GeorgianaElena requested a review from jnywong July 31, 2026 09:00
@jnywong

jnywong commented Jul 31, 2026

Copy link
Copy Markdown
Member

YES please

@jnywong
jnywong merged commit 7b635ef into 2i2c-org:main Jul 31, 2026
2 checks passed
@GeorgianaElena
GeorgianaElena deleted the envFromSecret branch July 31, 2026 11:33
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.

2 participants