search

apache / camel-k

Apache Camel K is a lightweight integration platform, born on Kubernetes, with serverless superpowers
https://camel.apache.org/camel-k
Apache License 2.0
865 stars 345 forks source link

Wrong behavior of global mode wrt kaniko cache warmer and platform #984

Closed nicolaferraro closed 5 years ago

nicolaferraro commented 5 years ago

When doing kamel install --global, the operator should be installed in global mode in the current namespace (message should mention the "global" mode) and I think there's no need to create the integration platform there, since you're going to create an integration platform in other ns probably (the fact that platform has not been installed can be also mentioned).

The strange thing I've noticed is that the kaniko warmer is started in the namespace where I install the global operator.

But when I run kamel install --skip-operator-setup in another ns, no warmer pod is started.

astefanutti commented 5 years ago

Currently, the Kaniko warmer pod is co-located with the operator so that it can be co-located with build pods, to share the default host path persistent volume.

I think we could create one Kaniko warmer pod per integration platform, then co-locate build pods with the corresponding warmer pod.

nicolaferraro commented 5 years ago

Yeah, there's no need in general to co-locate it with operator since we don't use the routine build process anymore on kube