squakez commented on code in PR #4942:
URL: https://github.com/apache/camel-k/pull/4942#discussion_r1410186010
##########
pkg/cmd/operator/operator.go:
##########
@@ -188,7 +188,6 @@ func Run(healthPort, monitoringPort int32, leaderElection
bool, leaderElectionID
selector := labels.NewSelector().Add(*hasIntegrationLabel)
selectors := map[ctrl.Object]cache.ByObject{
- &corev1.Pod{}: {Label: selector},
Review Comment:
Something else I thought is that we don't watch directly the Pods resource
at all. If we remove that capability we should be okey. I was already thinking
about this optimization because after all, we would always react on events on
the manager of those Pods (Deployment). The only cons is that we loose a finer
grain check and won't react on minor changes on managed Integration Pods (ie,
the user change some value directly on the Pod which does not affect the
Deployment). I can do some further testing on this part and we can discuss how
to progress once I have some test performed.
--
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-unsubscr...@camel.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
