timmy-mathew-ah opened a new issue, #6691: URL: https://github.com/apache/camel-k/issues/6691
### Bug description ### Bug Description With the fix provided in #6533 it fixed the hardcoded ClusterRole and ClusterRoleBinding issue when dealing with operator sharding apparently this issue has re-surfaced again due to hardcoded names in ClusterRoleBinding of registry-reader in [rbacs-common.yaml](https://github.com/apache/camel-k/blob/f25034da71810f698dcaa13b29049faa54a1692d/helm/camel-k/templates/rbacs-common.yaml#L186) This should also the same convention as applied for other RoleBinding and ClusterRoleBindings ``` apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRoleBinding metadata: labels: app: camel-k name: {{ include "camel-k.fullname" . }}-registry-reader-binding roleRef: apiGroup: rbac.authorization.k8s.io kind: ClusterRole name: {{ include "camel-k.fullname" . }}-registry-reader subjects: - kind: ServiceAccount name: {{ include "camel-k.fullname" . }}-operator namespace: '{{ .Release.Namespace }}' ``` I can provide a PR for this fix if this change looks fine. ### Camel K or runtime version v2.11.0-nightly -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
