<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "bug" label. For the Community Edition issue tracker: - https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=bug For the Enterprise Edition issue tracker: - https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary kubernetes account provided in KUBECONFIG is not in the right namespace when setting namespace with KUBE_NAMESPACE in CI settings ### Steps to reproduce Add a RBAC enabled kubernetes cluster to your project Set up $KUBE_NAMESPACE to whatever existing namespace in your kubernetes cluster.  set up a CI stage with an environment :  and try to apply a file in the cluster : kubectl apply -f ./file.yml --namespace $KUBE_NAMESPACE ### What is the current *bug* behavior?  user provided in $KUBECONFIG has no edit right in the $KUBE_NAMESPACE  and $KUBECONFIG content :  ### What is the expected *correct* behavior?  namespace should be $KUBE_NAMESPACE and this token should have edit rights in $KUBE_NAMESPACE ### Relevant logs and/or screenshots see previous screenshots ### Output of checks This bug happens on GitLab.com #### Results of GitLab environment info This bug happens on GitLab.com #### Results of GitLab application Check This bug happens on GitLab.com ### Possible fixes