We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When sealing the following secret:
apiVersion: v1 data: password: <elided> username: <elided> kind: Secret metadata: annotations: sealedsecrets.bitnami.com/cluster-wide: "true" name: keycloak type: Opaque
The resulting SealedSecret resource has the namespace set to "default".
apiVersion: bitnami.com/v1alpha1 kind: SealedSecret metadata: annotations: sealedsecrets.bitnami.com/cluster-wide: "true" creationTimestamp: null name: keycloak namespace: default spec: encryptedData: password: <elided> username: <elided> template: metadata: annotations: sealedsecrets.bitnami.com/cluster-wide: "true" creationTimestamp: null name: keycloak namespace: default type: Opaque status: {}
This makes it harder to use across namespaces as desired. Seems like in this case the resulting SealedSecret should have no namespace added.
The text was updated successfully, but these errors were encountered:
Merge #327
1049ebc
327: Refactor TestSeal to be table-driven r=mkmik a=mkmik In preparation to address #323 Co-authored-by: Marko Mikulicic <mkm@bitnami.com>
1a49e3f
GH misparsed a natural language sentence as a directive to close the issue 🤦♂
Sorry, something went wrong.
#328 contains the actual fix that would close the issue
Merge #328
ad6e649
328: Avoid materializing default namespace r=mkmik a=mkmik Closes #323 Co-authored-by: Marko Mikulicic <mkm@bitnami.com>
68ff559
Successfully merging a pull request may close this issue.
When sealing the following secret:
The resulting SealedSecret resource has the namespace set to "default".
This makes it harder to use across namespaces as desired. Seems like in this case the resulting SealedSecret should have no namespace added.
The text was updated successfully, but these errors were encountered: