Introduction
Fleet is currently alpha quality and actively being developed.
Fleet is GitOps at scale. Fleet is designed to manage up to a million clusters. It's also lightweight
enought that is works great for a single cluster too, but it really shines
when you get to a large scale. By large scale we mean either a lot of clusters, a lot of deployments, or a lot of
teams in a single organization.
Fleet can manage deployments from git of raw Kubernetes YAML, Helm charts, or Kustomize or any combination of the three.
Regardless of the source all resources are dynamically turned into Helm charts and Helm is used as the engine to
deploy everything in the cluster. This give a high degree of control, consistency, and auditability. Fleet focuses not only on
the ability to scale, but to give one a high degree of control and visibility to exactly what is installed on the cluster.# Quick Start
Quick Start
Who needs documentation, lets just run this thing!
Install
Get helm if you don't have it. Helm 3 is just a CLI and won't do bad insecure
things to your cluster.
brew install helm
Install the Fleet Helm charts (there's two because we separate out CRDs for ultimate flexibility.)
VERSION=0.3.0-alpha7
helm -n fleet-system install --create-namespace --wait \
fleet-crd https://github.com/rancher/fleet/releases/download/v${VERSION}/fleet-crd-${VERSION}.tgz
helm -n fleet-system install --create-namespace --wait \
fleet https://github.com/rancher/fleet/releases/download/v${VERSION}/fleet-${VERSION}.tgz
Add a Git Repo to watch
Change spec.repo
to your git repo of choice. Kubernetes manifest files that should
be deployed should be in /manifests
in your repo.
cat > example.yaml << "EOF"
apiVersion: fleet.cattle.io/v1alpha1
kind: GitRepo
metadata:
name: sample
# This namespace is special and auto-wired to deploy to the local cluster
namespace: fleet-local
spec:
# Everything from this repo will be ran in this cluster. You trust me right?
repo: "https://github.com/fleet-demo/simple"
EOF
kubectl apply -f example.yaml
Get Status
Get status of what fleet is doing
kubectl -n fleet-local get fleet
You should see something like this get created in your cluster.
kubectl get deploy frontend
NAME READY UP-TO-DATE AVAILABLE AGE
frontend 3/3 3 3 116m
Enjoy and read the docs.