-
Notifications
You must be signed in to change notification settings - Fork 3
init-secrets job #142
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
init-secrets job #142
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.
Looks really good and matches what I had in mind.
I think I'd like initSecrets.enabled: true
(or omitted as the default) on the <component>-minimal-values.yaml
as those are our examples of what is minimally required. I imagine there's issues with the manifest tests though?
charts/matrix-stack/configs/matrix-authentication-service/config.yaml.tpl
Outdated
Show resolved
Hide resolved
7614e69
to
2dbe596
Compare
042bdd5
to
f520581
Compare
f520581
to
3a5aec6
Compare
e0a1c43
to
409294f
Compare
- Add secret labels parameter to GenerateSecret function - Update secret creation and update logic to use new parameter - Validate if secret is managed by matrix-tools-init-secrets before updating - Adjust test cases to reflect new functionality - Refactor test case structure for clarity
- Validate secrets with new rules - Update job to pass generated secrets as labels - Modify service account conditionally based on secret generation - Simplify secret path resolution templates - Ensure consistent secret property checks across components
- Clarify required context properties in credentials template - Ensure init secrets are included when initSecrets enabled - Correctly reference postgres password secret property - Remove unnecessary job from service account test case - Simplify synapse statefulset init container configuration
b351657
to
8722622
Compare
8722622
to
960e15a
Compare
matrixTools: | ||
image: | ||
pullPolicy: Never | ||
digest: "" | ||
|
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.
Why is this needed in the EW integration test values?
This job is dedicated to initializing secrets when they are missing from the chart.
The job is enabled by default. It makes some secrets optional as they are going to be handled automatically during initial chart setup.
So far this PR makes the following secret optional :
synapse.macaroon
The PR adds 2 new helpers to include secrets in
matrix-tools
init containers.