From e0087cf65a464debd5c0fbd9f99ae01837559fac Mon Sep 17 00:00:00 2001 From: Mario Manno Date: Wed, 2 Jul 2025 17:27:28 +0200 Subject: [PATCH] Add note about Fleet CLI deploy These two pages (ref-bundle-stages and bundle-add) are closely related, so I added a note to the bundle-add page about the Fleet CLI. --- docs/bundle-add.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/bundle-add.md b/docs/bundle-add.md index 3f0c9ace0..1f40a5345 100644 --- a/docs/bundle-add.md +++ b/docs/bundle-add.md @@ -4,8 +4,13 @@ Bundles are automatically created by Fleet when a `GitRepo` is created. In most manually by the user. If you want to deploy resources from a git repository use a [GitRepo](https://fleet.rancher.io/gitrepo-add) instead. + If you want to deploy resources without a git repository follow this guide to create a `Bundle`. +:::note +If you want to deploy resources without running a Fleet controller, also take a look at the [Fleet CLI](ref-bundle-stages#examining-the-bundle-lifecycle-with-the-cli). +::: + When creating a `GitRepo` Fleet will fetch the resources from a git repository, and add them to a Bundle. When creating a `Bundle` resources need to be explicitly specified in the `Bundle` Spec. Resources can be compressed with gz. See [here](https://github.com/rancher/rancher/blob/main/pkg/controllers/provisioningv2/managedchart/managedchart.go#L149-L153)