Unable to set env var OPERATOR_ID in Helm installation

[daniel-geiger-ibmde]

As per https://camel.apache.org/camel-k/1.10.x/installation/advanced/multi.html the env var OPERATOR_ID must be set on the operator deployment to set the operator id. However the current helm chart doesn't expose the option to set any custom env vars in templates/operator.yaml.

In addition, default behaviour as described at https://camel.apache.org/camel-k/1.10.x/installation/advanced/multi.html does not apply - at least when deploying operator and integrations to a namespace other than camel-k:
Any Integration CRs annotated with the default "camel.apache.org/operator.id: camel-k" won't get picked up by the operator without OPERATOR_ID env variable set. The operator will only pick up the Integration CR after (manually) deleting the annotation. (So it seems the default operator-id is NULL rather than "camel-k".)

[christophd]

Hi,

there is a bug with OPERATOR_ID env var that will be fixed in v1.10.1 (see #3657)

There is a workaround to set KAMEL_OPERATOR_ID env var. With that the operator should start to pick up the integrations annotated with camel.apache.org/operator.id: camel-k.

With the upcoming fix in v1.10.1 both OPERATOR_ID and KAMEL_OPERATOR_ID will work as expected.

However this only solves on part of your problem. The missing option on the Helm chart still is a problem. I guess you would expect the Helm chart to set the default OPERATOR_ID=camel-k in addition to let the user specify another id, right?

[daniel-geiger-ibmde]

Hi Christoph, thanks for responding so quickly :-)

I totally agree regarding the helm chart. A new optional helm variable operator.id with a default value of camel-k would be most clear... at least to me ;-)

Regarding explanation of the default "camel-k" at https://camel.apache.org/camel-k/1.10.x/installation/advanced/multi.html: I think a brief hint could be helpful, that there will be no default operator id if neither of the env variables OPERATOR_ID or KAMEL_OPERATOR_ID is set. (From the current wording, one could assume that the default is implemented somewhere in the operator itself.)

[MehrCurry]

I have seen the fix in #3657. But it seems again that the helm chart has no possibility to set the environment variables. I missed i something?

[daniel-geiger-ibmde]

@MehrCurry - this is the fix.

Works like a charm - thanks guys! :-)