K8s Rizz Check v1.0.6
K8s Rizz Check now speaks EKS, AKS, and plain kubeconfig, not just GKE - and finding your clusters across all of them is a single zero-config step.
Multi-cloud support: EKS, AKS, and Kubernetes (kubeconfig)
Added first-class support for AWS EKS, Azure AKS, and a generic Kubernetes provider that reads whatever's already in your ~/.kube/config - kind, minikube, k3s, Rancher, on-prem, anything with a working context. All four providers (GKE, EKS, AKS, Kubernetes) now share the same zero-config bootstrap: run the app with no config.yaml, and it scans every cloud CLI you're logged into plus your local kubeconfig, then writes out a ready-to-use config.
Provider drawer redesign
The provider list is down to exactly the four real providers - GKE, EKS, AKS, Kubernetes - each with its own icon and an accurate "connected" status pulled straight from live cluster discovery, not a guess. The old K3s and Personal Clusters stub entries are gone; those cluster types already show up under Kubernetes automatically, since it just reads your kubeconfig.
EKS cluster discovery bug fix
EKS auto-discovery was silently finding zero clusters on some accounts due to a wrong field name when parsing AWS's API response. Fixed, and confirmed against a real EKS cluster.
Cluster list and per-cluster settings in config.yaml
config.yaml now lists every discovered cluster under its environment (name + location), written once at first-run bootstrap. Any setting - refresh interval, warning/critical thresholds, namespace blocklist, discovery interval - can now be overridden per cluster or per environment, with cluster-level overrides winning over environment-level ones, which win over the global defaults.
No action needed for existing config.yaml files - everything above is additive.