Creating a New Namespace
Explore how to create and use Kubernetes namespaces to manage multiple application releases in a single cluster. Understand context switching and namespace verification to isolate environments for testing and deployment efficiently.
Understanding the scenario
Currently, we’re running the release 1.0 of the go-demo-2 application. We can consider it the production release. Now, let’s say that the team in charge of the application makes new release. They run unit tests and build the binary. They produce a new Docker image and tag it as vfarcic/go-demo-2:2.0.
What they didn’t do is run functional, performance, and other types of tests that require a running application. The new release is still not ready to be deployed to production, so we cannot yet execute a rolling update and replace the production release with the new one. We need to finish running the tests, and for that we need the new release running in parallel with the old one.
Exploring our options
We could, for example, create a new cluster that would be used only for testing purposes. While that ...