For Elastisys Managed Services Customers
You can order a new environment by filing a service ticket.
If you have multiple Environments, and one or more have been clearly designated to be non-production Environments, Elastisys will apply major and minor updates to your non-production Environment(s) at least five working days before applying said update to your production Environment(s).
For more information, please read ToS 3.5 Updates and Upgrades.
Compliant Kubernetes recommends to setting up at least two separate environments: one for testing and one for production.
How Many Environments?¶
Many regulations require strict separation between testing and production environments. In particular, production data should not be compromised, no matter what happens in testing environments.
Similarly, some regulations -- such as Medical Devices Regulation (MDR) -- require you to take a risk-based approach to changing the tech stack. Depending on your risk assessment, this implies verifying changes in a non-production environment before going into production.
Therefore, Compliant Kubernetes recommends setting up at least two environments:
- staging;
- production.
However, the exact number of environments will depend on your needs. Please use the two figures below to reason about environments, trading developer productivity and data security:
