Your environment
Chart Version: 2.4.1
Helm Version: 4.0.4
Kubernetes Version: 1.32
What happened?
I'm deploying more than one Operator independent of the Connect server chart in a multi-tenant cluster. Each Operator covers several namespaces that users have access to. User need to create OnePasswordItems, but are Forbidden:
cannot get resource "onepassworditems" in API group "onepassword.com" in the namespace
What did you expect to happen?
User can create OnePasswordItems for the namespaces they have permission to.
Steps to reproduce
- Have Connect Server deployed separately and API available to cluster
- Deploy operator watching some set of namespaces. Use customized SA names for each.
- Have user with permission to the watched namespaces attempt to create OnePasswordItem for a namespaced secret.
Notes & Logs
Cluster is a Rancher managed, which automates the permission controls for multiple namespaces, grouping as a single object.
Not sure if this is too much of an edge case, but based on the documentation it appears to be a feasible use.
Your environment
Chart Version: 2.4.1
Helm Version: 4.0.4
Kubernetes Version: 1.32
What happened?
I'm deploying more than one Operator independent of the Connect server chart in a multi-tenant cluster. Each Operator covers several namespaces that users have access to. User need to create OnePasswordItems, but are Forbidden:
cannot get resource "onepassworditems" in API group "onepassword.com" in the namespaceWhat did you expect to happen?
User can create OnePasswordItems for the namespaces they have permission to.
Steps to reproduce
Notes & Logs
Cluster is a Rancher managed, which automates the permission controls for multiple namespaces, grouping as a single object.
Not sure if this is too much of an edge case, but based on the documentation it appears to be a feasible use.