nicolaferraro opened a new issue #1799: URL: https://github.com/apache/camel-k/issues/1799
I'm thinking to how we can improve global mode and I ended up with the following mechanism. When using global mode, the platform where the global Operator is installed (`camel-system` will be the one) should be the default for all namespaces. If a namespace has no platform (or it has a "empty" special platform, to deal with issues e.g. default kamelets are not installed in current namespace without a platform), then the global platform is used. The global platform imposes a global build strategy. A local integration kit is not processed locally, instead it is linked to a global kit. It can be linked to an existing global kit, or a new global kit can be created. Status of the local kit will mirror the status of the liked global kit. In the case of OpenShift, upon completion of the global kit, the imagestreams can be also copied over to the local namespace if needed. This way: - Builds are executed in the global namespace and existing kits are shared among all namespaces in the cluster - A local namespace can still have a custom platform, falling back to current way of working - There seems to be no way for a user in a namespace to "pollute" the global environment, hitting security issues Wdyt @astefanutti , @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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
