Skip to content
A CLI tool providing you with status & configuration of a Kubernetes cluster fleet
Go Makefile
Branch: master
Clone or download

Latest commit

mhausenblas Merge pull request #2 from naemono/add-oidc-auth
Adding oidc (dex style) authentication to fleet
Latest commit 76c0b8f Feb 14, 2020


Type Name Latest commit message Commit time
Failed to load latest commit information.
.github/workflows support releases through krew-release-bot Feb 9, 2020
cmd/fleet Merge branch 'master' of into add-oidc-auth Feb 14, 2020
deploy/krew update references to point to new org Feb 9, 2020
doc update usage doc Feb 9, 2020
.gitignore customizes template to init code base Nov 25, 2019
.goreleaser.yml update references to point to new org Feb 9, 2020
LICENSE Initial commit Nov 24, 2019
Makefile bumps to v0.1.4 Dec 31, 2019 update readme file Feb 10, 2020
go.mod update references to point to new org Feb 9, 2020
go.sum Initial commit Nov 24, 2019

Kubernetes cluster fleet viewer

Clusters are the new cattle and we should have tooling available that allows us to quickly get an idea what's going in a fleet of such clusters.

What is this about?

Meet fleet, a simple CLI tool that provides you with the status and configuration of a fleet of Kubernetes clusters. For example:

$ kubectl fleet
CLUSTER                                                      VERSION       NODES NAMESPACES PROVIDER      API
kind-kind-3                                                  v1.16.3       1/1   4          kind
test-cluster-2                                               v1.16.2       1/1   4          minikube
kind-test2                                                   v1.16.3       1/1   4          kind
minikube                                                     v1.16.2       1/1   4          minikube
gke_krew-release-bot-260708_us-central1-a_standard-cluster-1 v1.15.8-gke.3 3/3   4          GKE 
do-sfo2-k8s-1-16-6-do-0-sfo2-1581265844177                   v1.16.6       3/3   4          Digital Ocean

Above, you see fleet used as a kubectl plugin, available via krew. The top-level command lists all active clusters found in the kubeconfig provided. Active clusters are defined as the one that you would see when you'd execute the kubectl config get-contexts command. For each cluster, configuration info such as the control plane version or API server endpoint are displayed, as well as select stats, for example, the number of worker nodes or namespaces found in the cluster.

Note that you can also use it standalone, simply download the binary for your platform from the release page.

Getting started

To get started, visit the usage docs.

You can’t perform that action at this time.