Source: itnext.io
Self-Service Kubernetes Namespaces Are A Game-ChangerCategory: Kubernetes, artificial-intelligence
Self-service for namespaces will lead to a broader use of Kubernetes by engineers in any organization. Since Kubernetes has evolved dramatically, it is now not only a technology for operations anymore but also non-ops engineers can work with it.
In this article, I will describe what self-service namespaces are, why they are a game-changer for Kubernetes adoption, and how to get them.
However, it often makes sense to use a cluster that is similar to your production cluster (e.g. use AWS if your production cluster is AWS) because this makes development, testing, and other processes you want to use the self-service namespaces for more realistic.
loft is internally building on kiosk and, besides self-service namespaces on top of any connected cluster, it provides some useful additional features: It works with multiple clusters, has a GUI, a CLI, as well as a sleep mode to save cost, and it provides a virtual cluster technology that can be used to create self-service Kubernetes work environments that are even better isolated than namespaces.
In this article, I will describe what self-service namespaces are, why they are a game-changer for Kubernetes adoption, and how to get them.
However, it often makes sense to use a cluster that is similar to your production cluster (e.g. use AWS if your production cluster is AWS) because this makes development, testing, and other processes you want to use the self-service namespaces for more realistic.
loft is internally building on kiosk and, besides self-service namespaces on top of any connected cluster, it provides some useful additional features: It works with multiple clusters, has a GUI, a CLI, as well as a sleep mode to save cost, and it provides a virtual cluster technology that can be used to create self-service Kubernetes work environments that are even better isolated than namespaces.
Related Articles
Community Partners
DevOps Careers