base on Deploy workloads from Git to large fleets of Kubernetes clusters # Introduction [](https://app.fossa.com/projects/git%2Bgithub.com%2Francher%2Ffleet?ref=badge_shield) [](https://github.com/rancher/fleet/actions/workflows/ci.yml) [](https://github.com/rancher/fleet/actions/workflows/e2e-ci.yml) [](https://github.com/rancher/fleet/actions/workflows/e2e-multicluster-ci.yml) [](https://github.com/rancher/fleet/actions/workflows/golangci-lint.yml)  Fleet is GitOps at scale. Fleet is designed to manage multiple clusters. It's also lightweight enough that it 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 gives 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 For more information, have a look at Fleet's [documentation](https://fleet.rancher.io/). ## 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. For instance, using Homebrew: ``` brew install helm ``` Install the Fleet Helm charts (there's two because we separate out CRDs for ultimate flexibility.) ```shell helm -n cattle-fleet-system install --create-namespace --wait \ fleet-crd https://github.com/rancher/fleet/releases/download/v0.11.2/fleet-crd-0.11.2.tgz helm -n cattle-fleet-system install --create-namespace --wait \ fleet https://github.com/rancher/fleet/releases/download/v0.11.2/fleet-0.11.2.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. ```bash 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 run in this cluster. You trust me right? repo: "https://github.com/rancher/fleet-examples" paths: - simple EOF kubectl apply -f example.yaml ``` ## Get Status Get status of what Fleet is doing: ```shell 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](https://fleet.rancher.io/). ## License [](https://app.fossa.com/projects/git%2Bgithub.com%2Francher%2Ffleet?ref=badge_large) For developer and maintainer documentation, see [DEVELOPING.md](./DEVELOPING.md). ", Assign "at most 3 tags" to the expected json: {"id":"9122","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"