claudio4j opened a new pull request #2646: URL: https://github.com/apache/camel-k/pull/2646
Fix for #2642 This change enables to add custom labels to camel-k-operator at build time, allowing to set custom fixed labels which will be set on any pod. The developer should append this line to the `Makefile` to set the `AdditionalLabels` variable with the desired values, they are a map of key=values, separated by semi-colon (;) allowed characters are defined in [kubernetes doc](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#syntax-and-character-set). There is a special case, if the user wants to use the integration name, just put the value as `@integration@`, see example below. In this case, the pod will contains a label as "int-name" whose value is the integration name defined in runtime. ``` GOLDFLAGS += -X github.com/apache/camel-k/pkg/util/label.AdditionalLabels=department=Accounting;version=1.2.3;int-name=@integration@ ``` <!-- Enter your extended release note in the below block. If the PR requires additional action from users switching to the new release, include the string "action required". If no release note is required, write "NONE". You can (optionally) mark this PR with labels "kind/bug" or "kind/feature" to make sure the text is added to the right section of the release notes. --> **Release Note** ```release-note feat: Allow custom fixed labels for any running pod ``` -- 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]
