Shows you how to best manage and organize your application in Kubernetes namespaces. Walks through the evolution process that I've seen and also shows a full kubectl demo to help explain why an app-env based namespace naming strategy is good.
Wanted to also mentioned that prod and dev should be in separate clusters entirely. However, the naming strategy should still be the same and include the env. IE:
namespace = app1-dev.
The reason is because it’s common to have multiple envs in a common
non-prod cluster. By keeping the env in the namespace naming strategy, it's consistent for when the case comes up that folks want multiple environments in the same cluster, since there's some maintenance overhead that comes with managing each cluster.
Get full access to these great resources
All for less than the price of coffee a day