diff --git a/docs/gitrepo-add.md b/docs/gitrepo-add.md index 09bae2a86..48984d323 100644 --- a/docs/gitrepo-add.md +++ b/docs/gitrepo-add.md @@ -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. diff --git a/docs/namespaces.md b/docs/namespaces.md index 84fe07614..0574f1fd8 100644 --- a/docs/namespaces.md +++ b/docs/namespaces.md @@ -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 diff --git a/versioned_docs/version-0.4/gitrepo-add.md b/versioned_docs/version-0.4/gitrepo-add.md index 26274b1d9..dc7895a7b 100644 --- a/versioned_docs/version-0.4/gitrepo-add.md +++ b/versioned_docs/version-0.4/gitrepo-add.md @@ -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. diff --git a/versioned_docs/version-0.4/namespaces.md b/versioned_docs/version-0.4/namespaces.md index 64ef67397..11295bdb7 100644 --- a/versioned_docs/version-0.4/namespaces.md +++ b/versioned_docs/version-0.4/namespaces.md @@ -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 diff --git a/versioned_docs/version-0.4/troubleshooting.md b/versioned_docs/version-0.4/troubleshooting.md index 4818450f5..03b6fc433 100644 --- a/versioned_docs/version-0.4/troubleshooting.md +++ b/versioned_docs/version-0.4/troubleshooting.md @@ -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. \ No newline at end of file +... 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. diff --git a/versioned_docs/version-0.6/gitrepo-content.md b/versioned_docs/version-0.6/gitrepo-content.md index 32992a125..8f149389e 100644 --- a/versioned_docs/version-0.6/gitrepo-content.md +++ b/versioned_docs/version-0.6/gitrepo-content.md @@ -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. diff --git a/versioned_docs/version-0.6/namespaces.md b/versioned_docs/version-0.6/namespaces.md index f382b2590..ef6afb608 100644 --- a/versioned_docs/version-0.6/namespaces.md +++ b/versioned_docs/version-0.6/namespaces.md @@ -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 diff --git a/versioned_docs/version-0.7/gitrepo-add.md b/versioned_docs/version-0.7/gitrepo-add.md index 09bae2a86..d072a3ed0 100644 --- a/versioned_docs/version-0.7/gitrepo-add.md +++ b/versioned_docs/version-0.7/gitrepo-add.md @@ -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. diff --git a/versioned_docs/version-0.7/namespaces.md b/versioned_docs/version-0.7/namespaces.md index 84fe07614..0574f1fd8 100644 --- a/versioned_docs/version-0.7/namespaces.md +++ b/versioned_docs/version-0.7/namespaces.md @@ -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