nicolaferraro opened a new issue #2640: URL: https://github.com/apache/camel-k/issues/2640
It seems silly to scale an integration if it does not work, but now the error condition includes also pod failures. So if a container loses liveness because it receives too much traffic, then you can't scale the integration up. The number of replicas is not synced back into the deployment/ksvc when the phase is "Error", and we know it: https://github.com/apache/camel-k/blob/135020e97ad917bbab3dc8632804907c0ff98928/pkg/controller/integration/error.go#L95 What prevents us to just add "replicas" to the set of fields considered for the digest, so that when the number of replicas change the integration restarts from "Initialization"? All steps from "Initialization" to "Running" are idempotent, so why is there such a shortcut for the "replicas" field, just to keep the phase in "Running"? It often causes issues with the GC, like #2639 cc: @astefanutti , @squakez , @lburgazzoli -- 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
