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.
Master GitHub Actions with a Senior Infrastructure Engineer
As a senior staff infrastructure engineer, I share exclusive, behind-the-scenes insights that you won't find anywhere else. Get the strategies and techniques I've used to save companies $500k in CI costs and transform teams with GitOps best practices—delivered straight to your inbox.
Not sure yet? Check out the archive.
Unsubscribe at any time.