Most engineers prefer to work with Loft via the CLI because it allows them to create new namespaces and virtual clusters directly from the terminal of their IDE, immediately retrieve a local kube-context and start interacting with their Kubernetes environments.
Manage everything with kubectl
Loft's "Spaces" act as a virtual abstraction of Kubernetes namespaces ensure consistency and security.
Loft introcuces the Space as a custom resource. Spaces are virtual, so they don't actually get persisted in etcd but only exist as a virtual abstraction on top of regular namespaces. This has the benefit that there is no duplication but at the same time, you can manage spaces with kubectl just like regular Kubernetes namespaces but without the need to give users access to real namespaces or other cluster-wide resources.
Manually configuring RBAC is very risky because it is error-prone. Loft automated RBAC and reduces human errors while ensuring consistent security standards.
Loft allows platform admins to configure security templates for namespaces to enforce network isolation for namespaces using Kubernetes network policies.
Kubernetes ResourceQuotas are great but they work on a per-namespace basis. Loft allows you to define aggregated cross-namespace resource limits for indivual users, teams or AD/SSO groups.
Loft provides a secrets manager that allows you to define and sync secrets that should be available in all (or certain) namespaces.
