Distributions
KubeGlass works with any conformant Kubernetes cluster. It also recognises 29 distributions from the server version string, API groups and node labels, and shows the distribution’s name next to the Kubernetes version on the Overview. There is nothing to configure.
Cloud services
Section titled “Cloud services”Amazon EKS, Google Kubernetes Engine, Azure Kubernetes Service, Red Hat OpenShift on AWS (ROSA), Azure Red Hat OpenShift, Oracle Container Engine, DigitalOcean Kubernetes, Linode Kubernetes Engine, Scaleway Kapsule, Vultr Kubernetes Engine and Civo Kubernetes.
Self-managed
Section titled “Self-managed”Red Hat OpenShift, OKD, Rancher, Rancher RKE2, K3s, k0s, MicroK8s, Talos Linux and VMware Tanzu.
On your machine
Section titled “On your machine”Kind, k3d, Minikube, Docker Desktop, Rancher Desktop, Podman Desktop, OrbStack, Colima and CodeReady Containers.
Anything else shows as “Kubernetes” and works the same way.
What recognising the distribution changes
Section titled “What recognising the distribution changes”- All clusters and the cluster switcher show each cluster’s provider, and their filters match it.
- On OpenShift, Routes, DeploymentConfigs and the other OpenShift kinds are listed under Resources › Custom resources by API group, like any other kind the cluster serves.
Features that depend on installed components rather than the distribution, such as Gateway API, Argo CD, Flux, cert-manager or Prometheus, are found through API discovery on any cluster.