Don't use the default namespace in Kubernetes

If you’re using the default namespace in Kubernetes for application deployments, stop.

Even if you simply make a new namespace to dump everything into, I’d argue that is better than using the default namespace.

By using the default namespace, other engineers will start to make assumptions. Application deployments will begin to not make the namespace a variable.

It makes it more difficult to go from 1 to n.

If you’re using a non-default namespace, by the time you want to split things out into more namespaces, it’ll be easier. Your scripts, manifests, and pipelines will already have a variable for the namespace. The contract is already 80% of the way there.

Join the 80/20 DevOps Newsletter

If you're an engineering leader or developer, you should subscribe to my 80/20 DevOps Newsletter. Give me 1 minute of your day, and I'll teach you essential DevOps skills. I cover topics like Kubernetes, AWS, Infrastructure as Code, and more.

Not sure yet? Check out the archive.

Unsubscribe at any time.