astefanutti commented on issue #2188: URL: https://github.com/apache/camel-k/issues/2188#issuecomment-815595448
Ah I misunderstood it. Thanks for the clarification, now I think I got this right. So I think it's fixed with #2039, that introduces server-side apply to manage the Integration Deployment. The underlying issue lies in the way we process environment variables as a `map[string]string`, and Go explicitly randomises keys order, so that ultimately leads to Deployment revisions, hence ReplicaSets, for all possible combinations. Server-side apply is clever enough to handle the ordering differences, as it uses the environment variable name as merge key. Even if that is fixed with #2039, as a safe measure, I think it's still important that we avoid processing these environment variables as `map[string]string` and the resulting randomisation. -- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
