Centralised Operator Configuration (Feature)

[brianramseyau]

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
    ...