Skip to content

Community names/links updated to product names/links #1268

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
hardys merged 2 commits into from
Oct 15, 2026
Merged

Community names/links updated to product names/links #1268

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f1e7b9f
addressed conflicts after adding thr description tags
ranjinimn Oct 13, 2026
dcbb96c
modified the attributes to make it more crisp
ranjinimn Oct 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 10 additions & 7 deletions docs/en/components/fleet.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,8 @@
= Fleet
:description: Use Fleet to manage and deploy Kubernetes resources from Git using Helm, and monitor and control your clusters through the Rancher UI
:revdate: 2025-05-20
= SUSE(R) Rancher Prime: Continuous Delivery (Fleet)
:revdate: 2026-10-07
:revnumber: 3.7
:page-revdate: {revdate}
:experimental:
Expand All @@ -17,15 +19,16 @@ endif::[]

:imagesdir: ../images/

https://fleet.rancher.io[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.
{link-continuous-delivery-docs}/en/index.html[SUSE(R) Rancher Prime: Continuous Delivery (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.

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.

For information about how Fleet works, see https://ranchermanager.docs.rancher.com/{rancher-docs-version}/integrations-in-rancher/fleet/architecture[Fleet Architecture].
For information about how Continuous Delivery works, see {link-rancher-manager-docs}/en/integrations/fleet/architecture.html[SUSE® Rancher Prime: Continuous Delivery Architecture].


== Installing Fleet with Helm

Fleet comes built-in to Rancher, but it can be also https://fleet.rancher.io/installation[installed] as a standalone application on any Kubernetes cluster using Helm.
Fleet comes built-in to Rancher, but it can be also {link-continuous-delivery-docs}/en/tutorials/quickstart.html[installed] as a standalone application on any Kubernetes cluster using Helm.

== Using Fleet with Rancher

Expand Down Expand Up @@ -91,7 +94,7 @@ image::fleet-create-repo2.png[scaledwidth=100%]

== Debugging and troubleshooting

The "Advanced" navigation section provides overviews of lower-level Fleet resources. https://fleet.rancher.io/ref-bundle-stages[A bundle] is an internal resource used for the orchestration of resources from Git. When a Git repo is scanned, it produces one or more bundles.
The "Advanced" navigation section provides overviews of lower-level Fleet resources. {link-continuous-delivery-docs}/en/explanations/ref-bundle-stages.html[A bundle] is an internal resource used for the orchestration of resources from Git. When a Git repo is scanned, it produces one or more bundles.

To find bundles relevant to a specific repository, go to the Git repo detail page and click the `Bundles` tab.

Expand All @@ -102,10 +105,10 @@ A graph of *Repo > Bundles > BundleDeployments* is loaded. Click the BundleDeplo

image::fleet-repo-graph.png[scaledwidth=100%]

For additional information on Fleet troubleshooting tips, refer https://fleet.rancher.io/troubleshooting[here].
For additional information on Fleet troubleshooting tips, refer {link-continuous-delivery-docs}/en/troubleshooting.html[Troubleshooting].

== Fleet examples

The Edge team maintains a https://github.com/suse-edge/fleet-examples[repository] with examples of installing Edge projects with Fleet.
The Edge team maintains a https://github.com/suse-edge/fleet-examples[Github fleet repository] with examples of installing Edge projects with Fleet.

The Fleet project includes a https://github.com/rancher/fleet-examples[fleet-examples] repository that covers all use cases for https://fleet.rancher.io/gitrepo-content[Git repository structure].
The Fleet project includes a https://github.com/rancher/fleet-examples[fleet-examples] repository that covers all use cases for {link-continuous-delivery-docs}/en/explanations/gitrepo-content.html[Git repository structure].
25 changes: 13 additions & 12 deletions docs/en/components/system-upgrade-controller.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@
= System Upgrade Controller
:description: Install the System Upgrade Controller using Fleet GitRepo or Bundle resources to manage node upgrades and Day 2 operations in your cluster
:revdate: 2025-02-24
:revdate: 2026-10-07
:revnumber: 3.7
:page-revdate: {revdate}

Expand Down Expand Up @@ -39,7 +40,7 @@ Starting with Rancher link:https://github.com/rancher/rancher/releases/tag/v2.10
Follow the steps below *only* if your environment is *not* managed by Rancher, or if your Rancher version is lesser than `v2.10.0`.
====

We recommend that you install SUC through <<components-fleet, Fleet>> located in the link:https://github.com/suse-edge/fleet-examples[suse-edge/fleet-examples] repository.
We recommend that you install SUC through <<components-fleet>> located in the link:https://github.com/suse-edge/fleet-examples[suse-edge/fleet-examples] repository.

[NOTE]
====
Expand All @@ -57,18 +58,18 @@ This section covers:
[#components-system-upgrade-controller-fleet]
=== System Upgrade Controller Fleet installation

Using Fleet, there are two possible resources that can be used to deploy SUC:
Using Continuous Delivery (Fleet), there are two possible resources that can be used to deploy SUC:

* link:https://fleet.rancher.io/ref-gitrepo[GitRepo] resource - for use cases where an external/local Git server is available. For installation instructions, see <<components-system-upgrade-controller-fleet-gitrepo, System Upgrade Controller installation - GitRepo>>.
* {link-continuous-delivery-docs}/en/reference/ref-gitrepo.html[GitRepo] resource - for use cases where an external/local Git server is available. For installation instructions, see <<components-system-upgrade-controller-fleet-gitrepo, System Upgrade Controller installation - GitRepo>>.

* link:https://fleet.rancher.io/bundle-add[Bundle] resource - for air-gapped use cases that do not support a local Git server option. For installation instructions, see <<components-system-upgrade-controller-fleet-bundle, System Upgrade Controller installation - Bundle>>.
* {link-continuous-delivery-docs}/en/how-tos-for-users/bundle-add.html[Bundle] resource - for air-gapped use cases that do not support a local Git server option. For installation instructions, see <<components-system-upgrade-controller-fleet-bundle, System Upgrade Controller installation - Bundle>>.

[#components-system-upgrade-controller-fleet-gitrepo]
==== System Upgrade Controller installation - GitRepo

[NOTE]
====
This process can also be done through the Rancher UI, if such is available. For more information, see link:https://ranchermanager.docs.rancher.com/{rancher-docs-version}/integrations-in-rancher/fleet/overview#accessing-fleet-in-the-rancher-ui[Accessing Fleet in the Rancher UI].
This process can also be done through the Rancher UI, if such is available. For more information, see {link-rancher-manager-docs}/en/integrations/fleet/overview.html#_accessing_fleet_product_name_in_the_rancher_ui[Accessing Fleet in the Rancher UI].
====

In your *management* cluster:
Expand All @@ -79,7 +80,7 @@ In your *management* cluster:

** `fleet-default` - for resources that need to be deployed on *downstream* clusters.
+
For more information on Fleet workspaces, see the link:https://fleet.rancher.io/namespaces#gitrepos-bundles-clusters-clustergroups[upstream] documentation.
For more information on Fleet workspaces, see the {link-continuous-delivery-docs}en/explanations/namespaces.html#_gitrepos_bundles_clusters_clustergroups[SUSE(R) Rancher Manager] documentation.

. Deploy the `GitRepo` resource:

Expand All @@ -104,7 +105,7 @@ EOF
+
[NOTE]
====
Before deploying the resource below, you *must* provide a valid `targets` configuration, so that Fleet knows on which downstream clusters to deploy your resource. For information on how to map to downstream clusters, see link:https://fleet.rancher.io/gitrepo-targets[Mapping to Downstream Clusters].
Before deploying the resource below, you *must* provide a valid `targets` configuration, so that Fleet knows on which downstream clusters to deploy your resource. For information on how to map to downstream clusters, see {link-continuous-delivery-docs}/en/how-tos-for-users/gitrepo-targets.html[Mapping to Downstream Clusters].
====
+
[,bash,subs="attributes,specialchars"]
Expand Down Expand Up @@ -150,7 +151,7 @@ system-upgrade-controller 1/1 1 1 2m20s
[#components-system-upgrade-controller-fleet-bundle]
==== System Upgrade Controller installation - Bundle

This section illustrates how to build and deploy a `Bundle` resource from a standard Fleet configuration using the link:https://fleet.rancher.io/cli/fleet-cli/fleet[fleet-cli].
This section illustrates how to build and deploy a `Bundle` resource from a standard Fleet configuration using the {link-continuous-delivery-docs}/en/reference/cli/fleet-cli/fleet.html[fleet-cli].

. On a machine with network access download the `fleet-cli`:
+
Expand Down Expand Up @@ -204,7 +205,7 @@ cd fleet-examples/fleets/day2/system-upgrade-controller

** `fleet-default` - for resources that need to be deployed on *downstream* clusters.
+
For more information on Fleet workspaces, see the link:https://fleet.rancher.io/namespaces#gitrepos-bundles-clusters-clustergroups[upstream] documentation.
For more information on Fleet workspaces, see the {link-continuous-delivery-docs}/en/explanations/namespaces.html#_gitrepos_bundles_clusters_clustergroups[SUSE (R) Continuous Delivery] documentation.

. If you intend to deploy SUC only on downstream clusters, create a `targets.yaml` file that matches the specific clusters:
+
Expand All @@ -216,7 +217,7 @@ targets:
EOF
----
+
For information on how to map to downstream clusters, see link:https://fleet.rancher.io/gitrepo-targets[Mapping to Downstream Clusters]
For information on how to map to downstream clusters, see {link-continuous-delivery-docs}/en/how-tos-for-users/gitrepo-targets.html[Mapping to Downstream Clusters].

. Proceed to building the Bundle:
+
Expand All @@ -239,9 +240,9 @@ fleet-cli apply --compress -n fleet-local -o - system-upgrade-controller . > sys
fleet-cli apply --compress --targets-file=targets.yaml -n fleet-default -o - system-upgrade-controller . > system-upgrade-controller-bundle.yaml
----
+
For more information about this process, see link:https://fleet.rancher.io/bundle-add#convert-a-helm-chart-into-a-bundle[Convert a Helm Chart into a Bundle].
For more information about this process, see {link-continuous-delivery-docs}/en/how-tos-for-users/bundle-add.html[Convert a Helm Chart into a Bundle].
+
For more information about the `fleet-cli apply` command, see link:https://fleet.rancher.io/cli/fleet-cli/fleet_apply[fleet apply].
For more information about the `fleet-cli apply` command, see {link-continuous-delivery-docs}/en/reference/cli/fleet-cli/fleet_apply.html[fleet apply].

. Transfer the `system-upgrade-controller-bundle.yaml` bundle to your management cluster machine:
+
Expand Down
Loading
Loading