squakez commented on issue #3359: URL: https://github.com/apache/camel-k/issues/3359#issuecomment-1183059307
I had a look at this. I did not manage to replicate the issue. Actually it happens that when we do a `kamel rebuild` after a Camel K operator upgrade, the Integration.Status is wiped and a new IntegrationKit build is triggered as well (as the new operator version dependencies are different from the old ones). Which is the method we're using in the E2E tests to ask for a rebuild after an upgrade is 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
