This is an automated email from the ASF dual-hosted git repository. squakez pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/camel-k.git
commit 856ac03e2fba82f17ff0e5b4a85d4bc7aa21dea9 Author: dydydd <[email protected]> AuthorDate: Wed Sep 16 17:59:18 2026 +0800 Fix #6804: Propagate Camel Monitor label to Knative Service revision template The knative-service trait already carried the monitor label (CAMEL_MONITOR_OPERATOR_LABEL) on the Service top level via kubernetes.DeploymentLabels(), but the revision template Pod labels only contained the integration label, so Camel Dashboard discovery did not reach Knative workloads. Reuse DeploymentLabels() for the revision template, mirroring the deployment trait behavior. The camel.apache.org/integration label semantics are unchanged. Fixes https://github.com/apache/camel-k/issues/6804 --- pkg/trait/knative_service.go | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/pkg/trait/knative_service.go b/pkg/trait/knative_service.go index 3bbd6cf43..f384a4592 100644 --- a/pkg/trait/knative_service.go +++ b/pkg/trait/knative_service.go @@ -237,9 +237,10 @@ func (t *knativeServiceTrait) getServiceFor(e *Environment) (*serving.Service, e ConfigurationSpec: serving.ConfigurationSpec{ Template: serving.RevisionTemplateSpec{ ObjectMeta: metav1.ObjectMeta{ - Labels: map[string]string{ - v1.IntegrationLabel: e.Integration.Name, - }, + // DeploymentLabels propagates the Camel Monitor label + // (CAMEL_MONITOR_OPERATOR_LABEL) to the revision Pods, + // mirroring the deployment trait behavior. + Labels: kubernetes.DeploymentLabels(e.Integration.Name), Annotations: revisionAnnotations, }, Spec: serving.RevisionSpec{
