mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-05-05 20:53:33 +00:00
Billy Tat
74 lines
4.8 KiB
Markdown
74 lines
4.8 KiB
Markdown
---
|
|
title: Overview
|
|
---
|
|
|
|
<head>
|
|
<link rel="canonical" href="https://ranchermanager.docs.rancher.com/integrations-in-rancher/fleet/overview"/>
|
|
</head>
|
|
|
|
## What is Continuous Delivery with Fleet?
|
|
|
|
Continuous Delivery is Rancher's GitOps functionality, which is provided via integration with Fleet.
|
|
|
|
- *Cluster engine*: Fleet is a container management and deployment engine designed to offer users more control on the local cluster and constant monitoring through GitOps. Fleet focuses not only on the ability to scale, but it also gives users a high degree of control and visibility to monitor exactly what is installed on the cluster.
|
|
|
|
- *Deployment management*: Fleet can manage deployments from git of raw Kubernetes YAML, Helm charts, 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 all resources in the cluster. As a result, users can enjoy a high degree of control, consistency, and auditability of their clusters.
|
|
|
|
## Architecture
|
|
|
|
For information about how Fleet works, see the [Architecture](./architecture.md) page.
|
|
|
|
## Accessing Fleet in the Rancher UI
|
|
|
|
Fleet comes preinstalled in Rancher and is managed by the **Continuous Delivery** option in the Rancher UI. For additional information on Continuous Delivery and other Fleet troubleshooting tips, refer [here](https://fleet.rancher.io/troubleshooting).
|
|
|
|
Users can leverage continuous delivery to deploy their applications to the Kubernetes clusters in the git repository without any manual operation by following **gitops** practice.
|
|
|
|
Follow the steps below to access Continuous Delivery in the Rancher UI:
|
|
|
|
1. Click **☰ > Continuous Delivery**.
|
|
|
|
1. Select your namespace at the top of the menu, noting the following:
|
|
|
|
- By default, **fleet-default** is selected which includes all downstream clusters that are registered through Rancher.
|
|
|
|
- You may switch to **fleet-local**, which only contains the **local** cluster, or you may create your own workspace to which you may assign and move clusters.
|
|
|
|
- You can then manage clusters by clicking on **Clusters** on the left navigation bar.
|
|
|
|
1. Click on **Gitrepos** on the left navigation bar to deploy the gitrepo into your clusters in the current workspace.
|
|
|
|
1. Select your [git repository](https://fleet.rancher.io/gitrepo-add) and [target clusters/cluster group](https://fleet.rancher.io/gitrepo-targets). You can also create the cluster group in the UI by clicking on **Cluster Groups** from the left navigation bar.
|
|
|
|
1. Once the gitrepo is deployed, you can monitor the application through the Rancher UI.
|
|
|
|
## Windows Support
|
|
|
|
For details on support for clusters with Windows nodes, see the [Windows Support](./windows-support.md) page.
|
|
|
|
## GitHub Repository
|
|
|
|
The Fleet Helm charts are available [here](https://github.com/rancher/fleet/releases).
|
|
|
|
## Using Fleet Behind a Proxy
|
|
|
|
For details on using Fleet behind a proxy, see the [Using Fleet Behind a Proxy](./use-fleet-behind-a-proxy.md) page.
|
|
|
|
## Helm Chart Dependencies
|
|
|
|
In order for Helm charts with dependencies to deploy successfully, you must run a manual command (as listed below), as it is up to the user to fulfill the dependency list. If you do not do this and proceed to clone your repository and run `helm install`, your installation will fail because the dependencies will be missing.
|
|
|
|
The Helm chart in the git repository must include its dependencies in the charts subdirectory. You must either manually run `helm dependencies update $chart` or run `helm dependencies build $chart` locally, then commit the complete charts directory to your git repository. Note that you will update your commands with the applicable parameters
|
|
|
|
## Troubleshooting
|
|
|
|
- **Known Issue**: clientSecretName and helmSecretName secrets for Fleet gitrepos are not included in the backup nor restore created by the [backup-restore-operator](../../how-to-guides/new-user-guides/backup-restore-and-disaster-recovery/back-up-rancher.md#1-install-the-rancher-backup-operator). We will update the community once a permanent solution is in place.
|
|
|
|
- **Temporary Workaround**: By default, user-defined secrets are not backed up in Fleet. It is necessary to recreate secrets if performing a disaster recovery restore or migration of Rancher into a fresh cluster. To modify resourceSet to include extra resources you want to backup, refer to docs [here](https://github.com/rancher/backup-restore-operator#user-flow).
|
|
|
|
- **Debug logging**: To enable debug logging of Fleet components, create a new **fleet** entry in the existing **rancher-config** ConfigMap in the **cattle-system** namespace with the value `{"debug": 1, "debugLevel": 1}`. The Fleet application restarts after you save the ConfigMap.
|
|
|
|
## Documentation
|
|
|
|
See the [official Fleet documentation](https://fleet.rancher.io/) to learn more.
|