Cluster Updates under Administration shows where a cluster is, where it can go and what might block the way.
Providers
Kubyl detects the provider in a fixed order: OpenShift (ClusterVersion), EKS, GKE, AKS, k3s, RKE2, Cluster API and then self-managed, which is read-only. Override it with updates.clusters.<id>.provider (openshift, eks, gke, aks, k3s, rke2, cluster_api or self_managed).
What you see
- Current version, channel, update path, release notes, risks and conditions.
- OpenShift: ClusterOperators and machine config pools.
- k3s and RKE2: upgrade plans from system-upgrade-controller.
- EKS: add-ons. All providers: update history and How to update this cluster.
Pre-flight checks
- PodDisruptionBudgets that would block a drain.
- Deprecated APIs that are still being requested (from OpenShift APIRequestCount, else Prometheus, else the API server's
/metrics). - Removed APIs in Helm manifests and in last-applied configurations.
- Node headroom for a drain.
- Version skew and minor-by-minor update rules.
- Compatibility of installed operators.
| Keys | Action |
|---|---|
| R | Re-check |
| ShiftR | Re-run the pre-flight checks |
| U | Update… |
| JorKorUporDown | Select a version |
Update… asks for confirmation and is blocked on read-only clusters.