Skip to content
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

Centralised Operator Configuration (Feature) #47

Open
brianramseyau opened this issue Jul 25, 2024 · 0 comments
Open

Centralised Operator Configuration (Feature) #47

brianramseyau opened this issue Jul 25, 2024 · 0 comments

Comments

@brianramseyau
Copy link

Per the documentation, https://github.com/bitwarden/helm-charts/tree/main/charts/sm-operator#create-an-authorization-token-secret requiring a Secret for authorization per-namespace.

The requirement instead (at least the option of) one stored in the Operator's own namespace and used where possible is a little baffling, sure there would be some use cases where this is desired, but I feel those would be more edge-case and/or multi-tenant.

I request for the ability to store a Secret in the operators namespace which can be used (as default) for auth where no namespace-specific secrets are used/provided. Also happy to prefix the namespace to the spec.authToken.secretName like you do with, say, Istio gateways...

  ...
  authToken:
    secretName: sm-operator-system/bw-auth-token
    ... 
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

No branches or pull requests

1 participant