rancher
/
fleet-docs
mirror of https://github.com/rancher/fleet-docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fixing "\" due to markdown conversion

This commit is contained in:
hridyesh bisht 2025-07-16 12:01:49 +05:30
parent fc1cfa7d77
commit a050f3e402
No known key found for this signature in database
GPG Key ID: 7E30EC522B3FCFBB
1 changed files with 14 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
docs/cli/fleet-cli/install_fleet.md
View File

@ -17,11 +17,11 @@ Fleet CLI is a stand-alone binary you can download from the [Fleet GitHub releas
**Linux/macOS** **Linux/macOS**
```bash ```bash
curl \-L \-o fleet https://github.com/rancher/fleet/releases/download/v0.12.4/fleet-linux-amd64 curl -L -o fleet https://github.com/rancher/fleet/releases/download/v0.12.4/fleet-linux-amd64
\# Make it executable and move to PATH # Make it executable and move to PATH
chmod \+x fleet chmod +x fleet
sudo mv fleet /usr/local/bin/ sudo mv fleet /usr/local/bin/
``` ```
@ -29,13 +29,13 @@ sudo mv fleet /usr/local/bin/
**Windows (PowerShell)** **Windows (PowerShell)**
```bash ```bash
Invoke-WebRequest \-Uri "https://github.com/rancher/fleet/releases/download/v0.12.4/fleet-windows-amd64.exe" \-OutFile "fleet.exe" Invoke-WebRequest -Uri "https://github.com/rancher/fleet/releases/download/v0.12.4/fleet-windows-amd64.exe" -OutFile "fleet.exe"
``` ```
**Verify installation** **Verify installation**
```bash ```bash
fleet \--version fleet --version
``` ```
## **Prerequisites** ## **Prerequisites**
@ -52,7 +52,7 @@ Make sure you have the following tools installed and configured:
```bash ```bash
kubectl get nodes kubectl get nodes
helm version helm version
fleet \--version fleet --version
``` ```
# Install Fleet in Your Cluster # Install Fleet in Your Cluster
@ -76,11 +76,9 @@ kubectl create namespace cattle-fleet-system
### Step 2: Install Fleet CRDs and controller ### Step 2: Install Fleet CRDs and controller
```bash ```bash
\# Install Fleet # Install Fleet
helm install fleet-crd fleet/fleet-crd -n cattle-fleet-system --create-namespace --wait
helm upgrade \--install fleet-crd rancher-charts/fleet-crd \--namespace cattle-fleet-system helm install fleet fleet/fleet -n cattle-fleet-system --create-namespace --wait
helm upgrade \--install fleet rancher-charts/fleet \--namespace cattle-fleet-system
``` ```
### Step 3: Verify Fleet Is Running ### Step 3: Verify Fleet Is Running
@ -88,7 +86,7 @@ helm upgrade \--install fleet rancher-charts/fleet \--namespace cattle-fleet-sys
Check the pods in the cattle-fleet-system namespace: Check the pods in the cattle-fleet-system namespace:
```bash ```bash
kubectl get pods \-n cattle-fleet-system kubectl get pods -n cattle-fleet-system
``` ```
You should see pods like: You should see pods like:
@ -154,7 +152,7 @@ Each Fleet-managed cluster lists:
To validate whether your fleet apply created a bundle and if it’s deployed to the right number of target(s), run: To validate whether your fleet apply created a bundle and if it’s deployed to the right number of target(s), run:
```bash ```bash
kubectl get bundles.fleet.cattle.io \-A kubectl get bundles.fleet.cattle.io -A
``` ```
![A screenshot validating the fleet deployment.](/img/validate-deployment-ss.png) ![A screenshot validating the fleet deployment.](/img/validate-deployment-ss.png)
@ -170,7 +168,7 @@ If this field shows 1/1, the bundle is successfully deployed to one cluster.
To get a detailed view of how the bundle was rendered and applied: To get a detailed view of how the bundle was rendered and applied:
`kubectl get bundles.fleet.cattle.io \-n fleet-local my-nginx-bundle \-o yaml` `kubectl get bundles.fleet.cattle.io -n fleet-local my-nginx-bundle -o yaml`
Look for the following fields in the `status` section: Look for the following fields in the `status` section:
@ -182,7 +180,7 @@ status:
desiredReady: 1 desiredReady: 1
ready: 1 ready: 1
conditions: conditions:
\- type: Ready type: Ready
status: "True" status: "True"
``` ```
@ -194,7 +192,7 @@ This indicates that:
You can also verify the corresponding `BundleDeployment` object, since each `BundleDeployment` corresponds to a target cluster. You can also verify the corresponding `BundleDeployment` object, since each `BundleDeployment` corresponds to a target cluster.
`kubectl get bundledeployments.fleet.cattle.io \-A` `kubectl get bundledeployments.fleet.cattle.io -A`
## **Troubleshooting** ## **Troubleshooting**