squakez commented on issue #5491: URL: https://github.com/apache/camel-k/issues/5491#issuecomment-2115171067
I had a quick look at the history of the project and talking to historical contributors and it seems that I was making confusion between the concept of a **build** (which trigger a new Build, IntegrationKit, etc...) and the **deploy**. The original design was done to make sure the operator don't rebuild until the user would trigger the build manually (`kamel rebuild`), while keeping the possibility to redeploy the Integration according the new operator specifications (ie, changes in the Deployment). To be noticed that the rollout of the new Pod is done in accordance with this principle and it is not even happening every upgrade, but only when the new operator deployment logic make the changes that are transparently applied to the Integration resources involved. I will take the opportunity and clarify this aspect adding the proper documentation. In any case, the general review of the upgrade process is something that could be discussed and redesigned in the wider scope of the multi tenancy work effort that is ongoing as it seems to be a key feature that the new model should be able to provide in a seamless way. -- 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]
