Kubernetes integration using wrong namespace

Summary

I added an existing kubernetes cluster to my project, including filling in the 'project namespace' setting. But GitLab goes ahead and creates another namespace 'gitlab-managed-apps' and uses this.

Steps to reproduce

1. Add cluster, including filling in the 'project namespace'
2. Install Tiller
3. Install GitLab Runner
4. Start a pipeline
5. See the pods are running in the namespace 'gitlab-managed-apps'

What is the current bug behavior?

pods/etc are created in another namespace, 'gitlab-managed-apps'

What is the expected correct behavior?

everything should be in the namespace specified. You asked what namespace I want you to use, why are you making other stuff? What if I have two projects connected to the same cluster, maybe even two separate gitlab installs, how is this going to work?

Possible fixes

I am assuming that if I was using 'auto dev ops' that stuff is what gets created in the namespace I specified. And I see the sense in separating these two things, but if thats the reason, there should be two boxes, 'auto dev ops namespace' and 'other stuff namespace'. GitLab shouldn't go creating stuff in a namespace of its own choosing.