kuberoutectl
Discover, organize, and route Kubernetes access across Azure, AWS, GCP, and kubeconfig — from one provider-agnostic CLI that keeps a local inventory of your clusters and credential health.
Discover → organize → route, across all four providers.
Discover
One sync per provider populates a local inventory of clusters, scopes, and credentials — no manual bookkeeping.
Health-aware
Every credential carries a health state — valid, expiring, expired, static — and a suggested next action.
Organize
Label targets and save selector-driven collections that span clouds and survive every resync.
Route
target use writes kubeconfig and points kubectl at the right cluster in one step.
Why kuberoutectl
Every extra cloud means another CLI, another identity, and a few more unreadable
~/.kube/config contexts. kuberoutectl collapses that into one local inventory
of what you can reach and whether it’s healthy — so you route kubectl to the
right cluster in seconds.
Quick Start
brew install ymedlop/tap/kuberoutectl # macOS — all install methods in the guide below
kuberoutectl doctor # is the provider CLI reachable?
kuberoutectl sync azure # discover clusters + credential health (also: aws | gcp | kubeconfig)
kuberoutectl target list # what can I reach, and is it healthy?
kuberoutectl target use <alias> # route kubectl at the right cluster
Learn more
- Installation — every platform: Homebrew, apt, Scoop, packages, manual.
- Provider guides — Azure · AWS · GCP · kubeconfig, step by step.
- Organizing: labels & collections — tag clusters and build selector-driven views.
- Command reference — every command and flag, generated from the CLI.
- Concepts & architecture — the domain model and design principles (ARCHITECTURE.md for depth).
- Contributing — source, building, and development workflow.