Environment Page Overview
An environment refers to a Kubernetes namespace that is completely isolated and self contained entity containing multiple application deployments and datasources.
Some examples of environments that our users prefer:​
1. Dev Environment​
Ideally dedicated for developers
to develop, play around and iterate.
2. Staging Environment​
Can also be called test/pre-prod/UAT environment
. Environments like these are created to test and validate code before the release.
3. Prod Environment​
The environment which is customer facing. This is what will power your user facing application deployments.
How to Create an Environment​
- Go to Humalect's console's dashboard.
- Click on
Environment
. - Click on
Create New Environment
button on the top right.
To know more about the steps to create an environment, visit Environment
Relationship between Kubernetes namespaces and Humalect's environment​
Humalect environments use Kubernetes namespaces under the hood. All your resources like deployments and datasources are created within a particular namespace that is linked to a specific environment. This allows for complete isolation without replicating additional infrastructure costs.
Best practices for environment management​
- Always create separate environments for your
dev
,staging
andproduction
workloads. - Start every change from dev environment and move towards higher environments.
- Follow proper testing and code quality methodology.
Troubleshooting​
Need help? Contact us