End-to-End Kubernetes with Rancher, RKE2, K3s, Fleet, Longhorn, and NeuVector

Understanding the Fleet Workflow: How Everything Fits Together

At a high level, the workflow begins when a user creates a GitRepo resource in Fleet. This repo contains the desired state of the clusters. You can think of it as a pointer to the repository that contains the configuration files.

# From the Fleet Manager cluster (Rancher/Workspace server)
# Output can be empty if no GitRepos are defined
kubectl -n fleet-default get gitrepo

This custom resource defines the location of the Git repository, the branch to monitor, and any authentication details required to access the repository. The Fleet Manager then starts monitoring the repository for changes.

When a commit is pushed to the repository, the gitjob-controller