Namespace creation fail in AutoDevops due to caps
Summary
There is a scenario in which the namespace is not lowercased for kubernetes and AutoDevops fails
Steps to reproduce
Create a project for AutoDevops with uppeercase characters and potentially in a group with uppercase characters. Do not set any namespace. When autodevops will try to create a separate namespace to run the chart it will fail.
Example Project
What is the current bug behavior?
Build fails due to namespace creation fail.
What is the expected correct behavior?
Namespace should be created successfully.
More specific
The problem appears in gitlab-ce 10.0.2 while using k8s 1.6.6 on Azure Container Services when autodevops ci yaml does:
function ensure_namespace() { kubectl describe namespace "$KUBE_NAMESPACE" || kubectl create namespace "$KUBE_NAMESPACE" }
Somehow KUBE_NAMESPACE arrives with caps. Turns out this happens when the default_namespace is being used and the project name and group contain caps.
There is a one word fix in this MR: !14642 (closed)