-
Notifications
You must be signed in to change notification settings - Fork 4
Lifecycle management for ExternalSecrets #16
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Large diffs are not rendered by default.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -4,23 +4,44 @@ global: | |
| kind: ClusterSecretStore | ||
| name: vault-backend | ||
|
|
||
| # -- One-shot ExternalSecret provisioning for keycloak-users. | ||
| # When oneShot is true, the keycloak-users ExternalSecret becomes an | ||
| # ArgoCD Sync hook with HookSucceeded and creationPolicy: Orphan. | ||
| # Orphan prevents ESO from setting an ownerReference on the Secret, | ||
| # so k8s GC will not cascade-delete the Secret when ArgoCD removes | ||
| # the ExternalSecret hook after sync. | ||
| # A PostSync Job in the wrapper chart (e.g. rh-keycloak in | ||
| # layered-zero-trust) then cleans up Secrets labeled | ||
| # secretCleanupLabel=delete. | ||
| # When oneShot is false (default), keycloak-users is a regular | ||
| # ExternalSecret with no hook annotations — the Secret and | ||
| # ExternalSecret persist. | ||
| # @default -- disabled (regular ExternalSecret, no hooks) | ||
| # -- Properties associated with ExternalSecret resources. | ||
| externalSecrets: | ||
| oneShot: false | ||
| creationPolicy: Owner | ||
| secretCleanupLabel: "validatedpatterns.io/cleanup" | ||
| acs: | ||
| creationPolicy: Owner | ||
| deletionPolicy: Retain | ||
| refreshPolicy: Periodic | ||
| annotations: {} | ||
| labels: {} | ||
| adminUser: | ||
| creationPolicy: Owner | ||
| deletionPolicy: Retain | ||
| refreshPolicy: Periodic | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. since we specified the refreshPolicy as Periodic, do we want to add the refreshInterval as configurable?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Let's add that in a subsequent PR if desired |
||
| annotations: {} | ||
| labels: {} | ||
| keycloakUsers: | ||
| creationPolicy: Owner | ||
| deletionPolicy: Retain | ||
| refreshPolicy: Periodic | ||
| annotations: {} | ||
| labels: {} | ||
| oidcClientSecret: | ||
| creationPolicy: Owner | ||
| deletionPolicy: Retain | ||
| refreshPolicy: Periodic | ||
| annotations: {} | ||
| labels: {} | ||
| postgresqlDb: | ||
| creationPolicy: Owner | ||
| deletionPolicy: Retain | ||
| refreshPolicy: Periodic | ||
| annotations: {} | ||
| labels: {} | ||
| rhtpa: | ||
| creationPolicy: Owner | ||
| deletionPolicy: Retain | ||
| refreshPolicy: Periodic | ||
| annotations: {} | ||
| labels: {} | ||
|
|
||
| # -- Default-deny NetworkPolicy for the keycloak namespace. | ||
| # When enabled, deploys a namespace-wide NetworkPolicy that blocks all ingress and egress | ||
|
|
||
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.
is it keycloak admin user? is it possible to add comments here referencing back to the templates?