What's Next?
Recap what we have learned so far and what we are going to learn next.
We'll cover the following
Summary#
Deploying test releases as part of a continuous deployment process is not the only usage of Namespaces. There can be many other situations when they are useful. We could, for example, give a separate Namespace to each team in our organization. Or we could split the cluster into Namespaces based on the type of applications (e.g., monitoring, continuous-deployment, back-end, and so on).
All in all, Namespaces are a handy way to separate the cluster into different sections. Some of the Namespaces we’ll create will be long-lasting while others, like testing Namespace from our examples, will be short-lived.
The real power behind Namespaces comes when they are combined with authorization policies and constraints. However, we did not yet explore those subjects so, for now, we’ll need to limit our Namespaces experience to their basic form.
ℹ️ If you’d like to know more about Namespaces, please explore Namespace v1 core API documentation.
The next chapter covers everything about securing the Kubernetes clusters.
