Since we're using a single cluster, we will create two namespaces, staging and production, to isolate the resources dedicated to each environment. In a real scenario, you would instead have two separate clusters, to mitigate the risk of a staging hiccup affecting the production application:
$ kubectl create namespace productionnamespace "production" created$ kubectl create namespace stagingnamespace "staging" created$ kubectl get namespacesNAME STATUS AGEdefault Active 31dkube-public Active 31dkube-system Active 31dproduction Active 45sstaging Active 52s
This time, we only used the kubectl command-line syntax to create the namespaces, because the only thing we had to configure was the namespace name. Nonetheless, we could ...
