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

Remove instructions to move local clusters

This commit is contained in:
raul 2023-07-10 11:11:34 +02:00 committed by Corentin Néau
parent e1ddf91599
commit 64175ac062
9 changed files with 6 additions and 50 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/gitrepo-add.md
View File

@ -16,14 +16,6 @@ Git repos are added to the Fleet manager using the `GitRepo` custom resource typ
- `Fleet-default` will contain all the downstream clusters that are already registered through Rancher.
- `Fleet-local` will contain the local cluster by default.
Users can create new workspaces and move clusters across workspaces. An example of a special case might be including the local cluster in the `GitRepo` payload for config maps and secrets (no active deployments or payloads).
:::warning Local Cluster
While it's possible to move clusters out of either workspace, we recommend that you keep the local cluster in `fleet-local`.
:::
If you are using Fleet in a [single cluster](./concepts.md) style, the namespace will always be **fleet-local**. Check [here](https://fleet.rancher.io/namespaces/#fleet-local) for more on the `fleet-local` namespace.
For a [multi-cluster](./concepts.md) style, please ensure you use the correct repo that will map to the right target clusters.

2
docs/namespaces.md
View File

@ -45,8 +45,6 @@ When fleet is installed the `fleet-local` namespace is created along with one `C
automatically target the `local` `Cluster`. The `local` `Cluster` refers to the cluster the Fleet manager is running
on.
**Note:** If you would like to migrate your cluster from `fleet-local` to `default`, please see this [documentation](./troubleshooting.md#migrate-the-local-cluster-to-the-fleet-default-cluster).
### cattle-fleet-system (system namespace)
The Fleet controller and Fleet agent run in this namespace. All service accounts referenced by `GitRepos` are expected

8
versioned_docs/version-0.4/gitrepo-add.md
View File

@ -6,14 +6,6 @@ Git repos are added to the Fleet manager using the `GitRepo` custom resource typ
- `Fleet-default` will contain all the downstream clusters that are already registered through Rancher.
- `Fleet-local` will contain the local cluster by default.
Users can create new workspaces and move clusters across workspaces. An example of a special case might be including the local cluster in the `GitRepo` payload for config maps and secrets (no active deployments or payloads).
:::warning
While it's possible to move clusters out of either workspace, we recommend that you keep the local cluster in `fleet-local`.
:::
If you are using Fleet in a [single cluster](./concepts.md) style, the namespace will always be **fleet-local**. Check [here](https://fleet.rancher.io/namespaces/#fleet-local) for more on the `fleet-local` namespace.
For a [multi-cluster](./concepts.md) style, please ensure you use the correct repo that will map to the right target clusters.

2
versioned_docs/version-0.4/namespaces.md
View File

@ -29,8 +29,6 @@ When fleet is installed the `fleet-local` namespace is created along with one `C
automatically target the `local` `Cluster`. The `local` `Cluster` refers to the cluster the Fleet manager is running
on.
**Note:** If you would like to migrate your cluster from `fleet-local` to `default`, please see this [documentation](./troubleshooting.md#migrate-the-local-cluster-to-the-fleet-default-cluster).
### cattle-fleet-system
The Fleet controller and Fleet agent run in this namespace. All service accounts referenced by `GitRepos` are expected

18
versioned_docs/version-0.4/troubleshooting.md
View File

@ -67,17 +67,6 @@ NAME READY STATUS RESTARTS AGE
fleet-controller-64f49d756b-n57wq 1/1 Running 0 3m21s
```
### Migrate the local cluster to the Fleet default cluster?
For users who want to deploy to the local cluster as well, they may move the cluster from `fleet-local` to `fleet-default` in the Rancher UI as follows:
- To get to Fleet in Rancher, click ☰ > Continuous Delivery.
- Under the **Clusters** menu, select the **local** cluster by checking the box to the left.
- Select **Assign to** from the tabs above the cluster.
- Select **`fleet-default`** from the **Assign Cluster To** dropdown.
**Result**: The cluster will be migrated to `fleet-default`.
### Enable debug logging for `fleet-controller` and `fleet-agent`?
Available in Rancher v2.6.3 (Fleet v0.3.8), the ability to enable debug logging has been added.
@ -223,4 +212,9 @@ When you see an error like the one below ...
Error opening a gzip reader for /tmp/getter154967024/archive: gzip: invalid header
```
... the content of the helm chart is incorrect. Manually download the chart to your local machine and check the content.
... the content of the helm chart is incorrect. Manually download the chart to your local machine and check the content.
### Migrate the local cluster to the Fleet default cluster workspace?
Users can create new workspaces and move clusters across workspaces.
It's currently not possible to move the local cluster from `fleet-local` to another workspace.

7
versioned_docs/version-0.6/gitrepo-content.md
View File

@ -19,13 +19,6 @@ Git repos are added to the Fleet manager using the `GitRepo` custom resource typ
- `Fleet-default` will contain all the downstream clusters that are already registered through Rancher.
- `Fleet-local` will contain the local cluster by default.
Users can create new workspaces and move clusters across workspaces. An example of a special case might be including the local cluster in the `GitRepo` payload for config maps and secrets (no active deployments or payloads).
:::warning Local Cluster
While it's possible to move clusters out of either workspace, we recommend that you keep the local cluster in `fleet-local`.
:::
If you are using Fleet in a [single cluster](./concepts.md) style, the namespace will always be **fleet-local**. Check [here](https://fleet.rancher.io/namespaces/#fleet-local) for more on the `fleet-local` namespace.

2
versioned_docs/version-0.6/namespaces.md
View File

@ -44,8 +44,6 @@ When fleet is installed the `fleet-local` namespace is created along with one `C
automatically target the `local` `Cluster`. The `local` `Cluster` refers to the cluster the Fleet manager is running
on.
**Note:** If you would like to migrate your cluster from `fleet-local` to `default`, please see this [documentation](./troubleshooting.md#migrate-the-local-cluster-to-the-fleet-default-cluster).
### cattle-fleet-system (system namespace)
The Fleet controller and Fleet agent run in this namespace. All service accounts referenced by `GitRepos` are expected

7
versioned_docs/version-0.7/gitrepo-add.md
View File

@ -16,13 +16,6 @@ Git repos are added to the Fleet manager using the `GitRepo` custom resource typ
- `Fleet-default` will contain all the downstream clusters that are already registered through Rancher.
- `Fleet-local` will contain the local cluster by default.
Users can create new workspaces and move clusters across workspaces. An example of a special case might be including the local cluster in the `GitRepo` payload for config maps and secrets (no active deployments or payloads).
:::warning Local Cluster
While it's possible to move clusters out of either workspace, we recommend that you keep the local cluster in `fleet-local`.
:::
If you are using Fleet in a [single cluster](./concepts.md) style, the namespace will always be **fleet-local**. Check [here](https://fleet.rancher.io/namespaces/#fleet-local) for more on the `fleet-local` namespace.

2
versioned_docs/version-0.7/namespaces.md
View File

@ -45,8 +45,6 @@ When fleet is installed the `fleet-local` namespace is created along with one `C
automatically target the `local` `Cluster`. The `local` `Cluster` refers to the cluster the Fleet manager is running
on.
**Note:** If you would like to migrate your cluster from `fleet-local` to `default`, please see this [documentation](./troubleshooting.md#migrate-the-local-cluster-to-the-fleet-default-cluster).
### cattle-fleet-system (system namespace)
The Fleet controller and Fleet agent run in this namespace. All service accounts referenced by `GitRepos` are expected