Configuring Namespaces in Environments
This feature requires an understanding of Kubernetes Namespaces and building deployment architectures that can utilize the isolation provided by namespaces. This is an advanced customization feature that may not be required in most cases.
Understanding the relationship between Environments and Namespaces.¶
The Platformer Console allows you to deploy and manage Applications and related configurations to an Environment.
By default, one Environment is mapped to one Kubernetes namespace.
i.e. All applications in one Environment are deployed to a specific namespace on your connected Kubernetes Clusters.
But depending on your requirements you can optionally create more complex isolation levels using Environments and namespaces.
- Create a namespace per application in an Environment.
- Create a namespace for a group of applications in an Environment.
The applications will still be deployed to the Environment, but by using this feature you can control the namespaces it is deployed to, underneath the hood (useful for configuring Network Security Policies etc. at a namespace level).
Platformer Console provides you with flexible tooling to configure any (or a combination) of these patterns for your deployments.
Creating multiple namespaces in an Environment.¶
- Environments > Select an Environment
- Environment Settings > Namespaces Tab
- Click Create
- The new namespace will be associated under this Environment and you can specify which namespace your want your application(s) deployed in when you create a new Application.
When a new namespace is created in an Environment, it will be created in all Clusters associated to that environment. Read more on Multi-cluster environments.