Create namespaces with Loft to automatically apply strict workload and tenant isolation which allows you to host multiple teams and their applications in the same clusters without running into conflicts and without compromising cluster security and availability.
For even better isolation and even more flexibility, you can create virtual Kubernetes clusters with Loft. Virtual clusters have their own Kubernetes API server and a separate data store, so they feel entirely like different clusters and can even have different Kubernetes versions, but under the hood the containers they create run inside the underlying cluster.
Loft provides integrations with popular CI/CD and declarative infrastructure management tools, so you can use Loft with your existing toolchain and implement your use case as quickly as possible.
Loft's advanced inactivity detection monitors when engineers are not working with their namespaces and virtual clusters, so you can define rules for automatically putting pre-production environments to sleep or even configure Loft to automatically delete them after a certain period of inactivity.
Once an engineer starts using a namespace again (e.g. run a kubectl command), Loft automatically restores the state of the namespace and the engineer can keep working.
