-
Notifications
You must be signed in to change notification settings - Fork 9
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
Provide confidential values as secret #71
Merged
mwallschlaeger
merged 14 commits into
zalf-rdm:main
from
52North:issue#70_externalize-secrets
Sep 10, 2023
Merged
Provide confidential values as secret #71
mwallschlaeger
merged 14 commits into
zalf-rdm:main
from
52North:issue#70_externalize-secrets
Sep 10, 2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Use existingSecretName to configure secret via external secret - rabbitmq uses its own naming syntax. We show them for convenience - fixing external database property Postgres secrets for external databases has to be added still
mwallschlaeger
requested changes
Sep 8, 2023
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.
see my two remarks on this. else i'm fine with the general idea on this now.
@@ -65,6 +65,8 @@ spec: | |||
envFrom: | |||
- configMapRef: | |||
name: {{ include "geoserver_pod_name" . }}-env | |||
- secretRef: | |||
name: {{ .Values.geoserver.secret.existingSecretName | "geoserver-secret" | quote }} |
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.
See comments on geonode-deploy.yaml herefor
mwallschlaeger
previously approved these changes
Sep 8, 2023
mwallschlaeger
added
documentation
Improvements or additions to documentation
feature
new required feature
labels
Sep 8, 2023
ridoo
changed the title
WIP: Provide confidential values as secret
Provide confidential values as secret
Sep 8, 2023
ridoo
commented
Sep 8, 2023
charts/geonode/templates/postgres/postgres-external-geonode-secrets.yaml
Outdated
Show resolved
Hide resolved
mwallschlaeger
requested changes
Sep 8, 2023
mwallschlaeger
approved these changes
Sep 10, 2023
mwallschlaeger
added a commit
that referenced
this pull request
Sep 11, 2023
* Issue#59 task prepare this repository to be available on artifact hub (#65) * Fixes [#59,#58] * Issue#27 py csw single microservice (#68) issue#27_csw_single_microsservice * Issue#67 separate site url related settings from ingress config (#69) issue#67_separate_site_url_related_settings_from_ingress_config * Provide confidential values as secret (#71) * WIP: Provide confidential values as secret * Fix parameter names in comment * Provide demo credentials as base64 * Add named secret in values.yaml with default content * Remove secret boilerplate in values.yaml * Configure secret creation via flag * Enhance secret configuration - Use existingSecretName to configure secret via external secret - rabbitmq uses its own naming syntax. We show them for convenience - fixing external database property Postgres secrets for external databases has to be added still * Fix yaml syntax * Fix yaml and property refs * Adds configurable secret to external database * Adjust minikube values * Resolve go template issues * Update documentation * Fix wording * release 1.0.0 final changes [geonode 4.1.2] (#74) release 1.0.0 * Issue#72 bug celery container is not starting properly and exiting right away (#76) * release 1.0.0 * fixing release build (#78) * added github token to install helm --------- Co-authored-by: Henning Bredel <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Separates confidential values (currently the superuser credentials) from
values.yaml
into a Kubernetes Secret.Provides a
templates/demo-secret.yaml
by default. However, can be overridden by a custom secret which can be referenced by name in thevalues.yaml
.@mwallschlaeger please have a look, if you think this is a path we may want to follow. If you are ok, I will continue refactoring the remaining credentials.
Type of Change
Please select the relevant option:
Related Issue
If there is an existing issue related to this pull request, please reference it here.
closes #70
Checklist
Please ensure that your pull request meets the following requirements:
Additional Notes
Any additional information or context regarding the pull request can be provided here.
Thank you for creating this pull request