You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "timmy-mathew-ah (via GitHub)" <gi...@apache.org> on 2026/03/16 01:30:13 UTC
[I] [Helm] Camel-K Operator sharding via Helm is broken. [camel-k]
timmy-mathew-ah opened a new issue, #6533:
URL: https://github.com/apache/camel-k/issues/6533
### Bug description
Installing multiple global Camel-K operators via Helm for operator sharding fails on the second helm install due to hardcoded ClusterRole and ClusterRoleBinding names in [rbacs-descoped.yaml](https://github.com/apache/camel-k/blob/main/helm/camel-k/templates/rbacs-descoped.yaml), reference line [here](https://github.com/apache/camel-k/blob/3773bc49e5a9172b6cd01728e5add6fbeb4fbdc0/helm/camel-k/templates/rbacs-descoped.yaml#L453) and same issue with other ClusterRoleBindings defined after in the file.
The [official documentation on multiple operators](https://camel.apache.org/camel-k/next/installation/advanced/multi.html) describes a multi-operator setup where each operator has a unique OPERATOR_ID and only reconciles resources annotated with the matching camel.apache.org/operator.id. However, the Helm chart cannot actually deploy this setup because all cluster-scoped RBAC resources use fixed names regardless of the Helm release name or operator.operatorId value.
**First install** (succeeds):
```bash
helm install camel-k-shard-1 camel-k/camel-k \
--create-namespace \
--namespace platform-camel-k-shard-1 \
--set-string operator.global=true \
--set operator.operatorId=camel-k-shard-1
```
**Second install** (fails):
```bash
helm install camel-k-shard-2 camel-k/camel-k \
--create-namespace \
--namespace platform-camel-k-shard-2 \
--set-string operator.global=true \
--set operator.operatorId=camel-k-shard-2
```
**Error:**
```
Error: INSTALLATION FAILED: unable to continue with install: ClusterRole "camel-k-operator" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-name" must equal "camel-k-shard-2": current value is "camel-k-shard-1"; annotation validation error: key "meta.helm.sh/release-namespace" must equal "platform-camel-k-shard-2": current value is "platform-camel-k-shard-1"
```
Issue #6145 reported this and it was seemed to be fixed by PR #6191 which removed several unnecessary cluster-scoped resources.
**However, the core problem still exists in `rbacs-descoped.yaml`** the template used when `operator.global=true`. All ClusterRole and ClusterRoleBinding names in this file are hardcoded and not parameterized by `{{ .Release.Name }}`, `{{ .Values.operator.operatorId }}`, or `{{ include "camel-k.fullname" . }}`.
The namespace being dynamic proves the intent was to support multiple installs in different namespaces so can the metadata.name be fixed in a similar way as described below to use `camel-k-operator-{{ .Release.Name }}` ? Happy to open a PR.
```
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
labels:
app: camel-k
name: camel-k-operator-{{ .Release.Name }} # ← unique per Helm release
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: camel-k-operator
subjects:
- kind: ServiceAccount
name: camel-k-operator
namespace: '{{ .Release.Namespace }}'
```
### Camel K or runtime version
v2.9.1
--
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: commits-unsubscribe@camel.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Helm] Camel-K Operator sharding via Helm is broken. [camel-k]
Posted by "timmy-mathew-ah (via GitHub)" <gi...@apache.org>.
timmy-mathew-ah commented on issue #6533:
URL: https://github.com/apache/camel-k/issues/6533#issuecomment-4133578738
Hey @squakez , now as the PR fix has been merged to main. Could you please confirm which upcoming Camel K release is expected to include it and if there is any tentative release timeline? We’re actively working on a project with Camel K and would love to make use of this change.
--
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: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Helm] Camel-K Operator sharding via Helm is broken. [camel-k]
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez closed issue #6533: [Helm] Camel-K Operator sharding via Helm is broken.
URL: https://github.com/apache/camel-k/issues/6533
--
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: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Helm] Camel-K Operator sharding via Helm is broken. [camel-k]
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #6533:
URL: https://github.com/apache/camel-k/issues/6533#issuecomment-4133624294
Hello, yest, the target is 2.10.0 and the tentatively planned date for it is the end of this month. We have a few pending issue I'd like to close during next weekend, and, after those we can plan the release, likely within the first two weeks of April.
--
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: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Helm] Camel-K Operator sharding via Helm is broken. [camel-k]
Posted by "squakez (via GitHub)" <gi...@apache.org>.
squakez commented on issue #6533:
URL: https://github.com/apache/camel-k/issues/6533#issuecomment-4067990225
Hello. That's correct, and it is what we are warning in https://camel.apache.org/camel-k/next/installation/advanced/multi.html#advanced-installation-caveat
For Helm it requires some change in the way the chart is generated. Making it unique via the suffix is what we're doing in the Kustomization case, so, happy to review the PR if you think this issue can be solved that way. Thanks!
--
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: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Helm] Camel-K Operator sharding via Helm is broken. [camel-k]
Posted by "timmy-mathew-ah (via GitHub)" <gi...@apache.org>.
timmy-mathew-ah commented on issue #6533:
URL: https://github.com/apache/camel-k/issues/6533#issuecomment-4114108542
Hey @squakez , thanks for your response :) I've created a [PR](https://github.com/apache/camel-k/pull/6543). If all goes well is it still in time for 2.10.0 ?
--
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: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [Helm] Camel-K Operator sharding via Helm is broken. [camel-k]
Posted by "timmy-mathew-ah (via GitHub)" <gi...@apache.org>.
timmy-mathew-ah commented on issue #6533:
URL: https://github.com/apache/camel-k/issues/6533#issuecomment-4200658544
@squakez I noticed that v2.10.0 was released recently, and according to the release notes, it includes the following change:
> fix(helm): parameterize resource names to enable multi-operator sharding via Helm
> (by @timmy-mathew-ah in https://github.com/apache/camel-k/pull/6543)
>
However, it seems that this fix is not actually part of the v2.10.0 release.
Could you clarify if there was any specific reason why this change wasn’t included?
--
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: commits-unsubscribe@camel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org