Kubernetes cluster integration shall only install Helm Tiller or Ingress if not available already
Scenario
The cluster integration feature also allows to install certain "auxiliary" Applications. This is currently Helm Tiller and Ingress (which is the Nginx Ingress controller)
Clicking install on Helm Tiller installs Tiller into a namespace called gitlab-managed-apps
.
But actually, I had already Helm Tiller as well as Ingress installed.
Helm Tiller specifically, was installed with the default method helm init
into the kube-system
namespace.
Impact
- Installing Ingress or Tiller twice can lead to confusion, as two deployments are competing to do the same work. For example, which Tiller will I talk to when I do
helm list
? - It is a waste of resources (CPU and memory)
Requests
- The Cluster Integration feature should be able to find out if any of these auxiliary applications has been installed already and not install it twice.
- It should note more specifically what will happen (install helm tiller into a dedicated namespace)