You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
add option to not install clusterrole for telemetry (#4133)
# Summary
- some customers might have multiple operators in the same cluster. If
yes, enabling telemetry would install the clusterrole (non-namespaced
resource) multiple times and fail
- this adds support for customers to not install the clusterrole as a
helm chart setting
## Proof of Work
no clusterrole
```
1.24.0 ~/projects/ops-manager-kubernetes better-helm-chart* kind-e2e-operator/nnguyen-evg-single 05:45:26 PM
❯ helm install operator helm_chart --set operator.telemetry.installClusterRoles=false
NAME: operator
LAST DEPLOYED: Wed Feb 26 17:45:30 2025
NAMESPACE: nnguyen-evg-single
STATUS: deployed
REVISION: 1
TEST SUITE: None
1.24.0 ~/projects/ops-manager-kubernetes better-helm-chart* kind-e2e-operator/nnguyen-evg-single 05:45:33 PM
❯ k get clusterrole | rg telemetry <--- none
```
clusterrole exists
```
❯ helm install operator helm_chart --set operator.telemetry.installClusterRoles=true
NAME: operator
LAST DEPLOYED: Wed Feb 26 17:47:38 2025
NAMESPACE: nnguyen-evg-single
STATUS: deployed
REVISION: 1
TEST SUITE: None
1.24.0 ~/projects/ops-manager-kubernetes better-helm-chart kind-e2e-operator/nnguyen-evg-single 05:47:42 PM
❯ k get clusterrole | rg telemetry
mongodb-enterprise-operator-cluster-telemetry 2025-02-26T16:47:40Z
```
## Checklist
- [ ] Have you linked a jira ticket and/or is the ticket in the title?
- [x] Have you checked whether your jira ticket required DOCSP changes?
- [x] Have you checked for release_note changes?
0 commit comments