multiple projects on same k8s cluster - does not work
Summary
When I setup kubernetes for my second project (with exact same values for everything - as for the first project) - and 'namespace' not set, gitlab creates a new namespace for the new project, but then fails with: Kubernetes error: Kubeclient::HttpError configmaps "values-content-configuration-helm" already exists
which seems to be because it still wants tiller to run in gitlab-managed-apps namespace - but does not recognize that it already installed that tiller service - for another project.
Possible fixes
kubernetes config should be available under "admin" settings (just as auto devops domain is) - so admin can set the user with the k8s-admin token there - and then each project, can just "enable" a k8s cluster - given from the admin list (or add their own directly as now).
If k8s cluster is setup centrally - then hopefully, that should mean it will detect already running tiller, and not try to roll out a new one in same namespace.