My sincere thanks for using the website!Henning May 6, 2017Q:React K8S Custom Resource requiring namespace value to be exactly setI am trying to set a custom resource in K8S, using this documentation:I want the namespace to be called asap-test-jenkins, but the API complains it's not valid because the name has to be exactly as specified.kubectl create -f asap-test-jenkins.jsonasap-test-jenkins.json: error: cannot validatespec.namespace: - must be exactly as specified (e.g. mynamespace.svc.cluster.local)I already tried several combinations of the namespace name, but none of them were accepted by the API.A:The documentation you link to is the old way of doing things.The namespace specified in a custom resource must be a DNS subdomain of one of the namespaces kubernetes attempts to create, and must exist at the time of the attempt. If the API server hostnames are not valid DNS names, they will be added to your current namespace in the form namespace.kubernetes.namespace.It seems that the API server has several alternate names for the default cluster namespace.API Server hostnames are assumed to be either:a hostname that ends in "kubernetes.default.svc" in the current DNS namespace (e.g. "kubernetes.default.svc.cluster.local")a hostname that resolves to "kubernetes" in the current DNS namespace (e.g. "cluster.local").If the former option is not a valid DNS name, it will be added to the current DNS namespace in the form namespace.default.svc.cluster.local. If this name is not recognized by kubectl, it will be added to the current DNS namespace in the form namespace.kubernetes.default.svc.cluster.local.If the API server hostnames are not valid DNS 08929e5ed8