Supported Distributions

KubeGlass auto-detects your Kubernetes distribution via version strings, API groups, and node labels. No per-distro configuration is required.

Cloud managed

Distribution	Provider	Detection method
Amazon EKS	AWS	Version string contains eks
Google GKE	Google Cloud	Version string contains gke
Azure AKS	Microsoft Azure	Version string or node labels
Red Hat OpenShift	Red Hat	OpenShift API groups present
Azure Red Hat OpenShift (ARO)	Microsoft / Red Hat	OpenShift + Azure node labels
ROSA	AWS / Red Hat	OpenShift + AWS node labels
IBM Cloud Kubernetes (IKS)	IBM	Version string or node labels
Oracle OKE	Oracle Cloud	Version string or node labels
DigitalOcean DOKS	DigitalOcean	Node labels
Linode LKE	Akamai/Linode	Node labels
Scaleway Kapsule	Scaleway	Node labels
OVHcloud MKS	OVHcloud	Node labels
Civo K3s	Civo	Node labels + k3s version
Vultr Kubernetes Engine	Vultr	Node labels

Self-managed

Distribution	Vendor	Detection method
Rancher RKE	SUSE	Version string or annotations
Rancher RKE2	SUSE	Version string
VMware Tanzu (TKG)	Broadcom	API groups or node labels
k3s	SUSE	Version string contains k3s
k0s	Mirantis	Version string contains k0s
MicroK8s	Canonical	Version string or snap labels
Charmed Kubernetes	Canonical	Juju annotations
Talos	Sidero Labs	Version string or node labels
Harvester	SUSE	API groups
Kubermatic	Kubermatic	Annotations

Local development

Distribution	Detection method
minikube	Node labels (minikube)
kind	Node labels (kind)
Docker Desktop	Version string or node name
Rancher Desktop	Version string + process detection
Colima	Node name patterns

What auto-detection enables

When a distribution is detected, KubeGlass:

• Shows the distribution logo and name in the cluster header
• Enables distribution-specific features (e.g., OpenShift Routes, EKS IAM integration)
• Adjusts health scan rules for distribution-specific components
• Provides distribution-aware documentation links

Compatibility matrix

The following matrix shows validated feature coverage by distribution. Features are verified against real clusters during each release cycle. ”—” means the feature is not applicable to that distribution, not that it is broken.

Distribution	K8s version	Detection	Workloads	Logs	Exec	Metrics	GitOps	Drift	RBAC	Fleet	Tracing
Amazon EKS	1.27–1.31	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
Google GKE	1.27–1.31	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
Azure AKS	1.27–1.31	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
Red Hat OpenShift	4.14–4.17	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
k3s	1.27–1.31	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
RKE2	1.27–1.31	✅	✅	✅	✅	✅	✅	✅	✅	✅	✅
kind	1.27–1.31	✅	✅	✅	✅	⚠️¹	✅	✅	✅	—	⚠️²
minikube	1.27–1.31	✅	✅	✅	✅	✅	✅	✅	✅	—	⚠️²
Docker Desktop	1.27–1.31	✅	✅	✅	✅	⚠️¹	✅	✅	✅	—	⚠️²

¹ Metrics server must be installed manually on local dev distributions. ² Tracing requires a Jaeger/OTLP backend to be deployed in the cluster.

Known gaps

• Cluster provisioning: KubeGlass does not create or upgrade clusters. Use your provider’s tooling (eksctl, gcloud, az aks, Rancher, etc.) for lifecycle management.
• Cloud IAM: Cloud-provider IAM policies are managed through cloud consoles, not KubeGlass.
• Catalog/marketplace: Rancher’s app catalog and Helm chart marketplace features are not replicated. KubeGlass focuses on day-2 operations, not app distribution.

Reporting compatibility issues

If you encounter a distribution-specific issue, file a GitHub issue with:

1. Distribution name and version
2. Kubernetes version
3. KubeGlass version
4. Feature affected and error message