astefanutti edited a comment on issue #2640: URL: https://github.com/apache/camel-k/issues/2640#issuecomment-920791367
The replicas field is already a bit special for Deployment, as it does not change the PodSpec hash, and does not trigger a rollout when changed. We kind of do the same thing for Integration. I'd be inclined to think core k8s developers had good reasons to do so, and I would find a bit weird to re-initialise an Integration when scaled. Now for the relation to GC, there are multiple things. In the context of #2639, I still think creating a Kit that's owned by the Integration in that case is a shortcut, see #2365. In the context of other issues about GC, AFAIR, it was about forgetting to add both `IntegrationPhaseDeploying` and `IntegrationPhaseRunning` phases. It turns out both are always added, so the question arises, what is the point of having both? I'm working on scaling right now as I've found issues in the context of #2443. So I can piggy-back any new issues related to scaling. -- 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
