public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-08-25 11:22:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

Say that it is not possible to detach non-imported clusters from Rancher

Browse Source
This commit is contained in:
Catherine Luse
2020-01-23 16:05:10 -07:00
parent 9e33310432
commit 0f43c2d258
2 changed files with 6 additions and 36 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.x/en/detaching-rancher/_index.md
-34
View File
@@ -1,34 +0,0 @@
---
title: Detaching Rancher from Downstream Clusters
weight: 7502
---
This section describes the options for disconnecting a downstream cluster from Rancher while still being able to use the cluster. For imported clusters, this result is achieved by deleting the cluster from the Rancher UI. For other types of clusters, we recommend using a third-party service to back up your Kubernetes applications, because the Rancher UI does not allow them to be deleted without also uninstalling Kubernetes from the cluster.
# Imported Clusters
If you use the Rancher UI to delete an imported cluster, the cluster is detached from Rancher, but not destroyed. You should still be able to use the cluster.
# Non-imported Clusters
For other types of clusters, if you use the Rancher UI to delete the cluster, Rancher uninstalls Kubernetes from the cluster and cleans the nodes so that they can be used for other purposes.
For clusters created in a hosted Kubernetes provider, such as EKS, GKE, or AKS, the ability to detach the cluster from Rancher without removing Kubernetes is a feature that will be added to Rancher in a future update.
For clusters in which Kubernetes was launched by Rancher, such as custom clusters, or clusters created in an infrastructure provider, it is not possible to detach the cluster from Rancher in a way that still allows you to use the cluster, and we don't plan to add that capability to Rancher. However, some third-party software solutions exist to help you backup and restore your cluster, such as Velero/Restic and Stashed.
If you need to detach non-imported clusters from Rancher while still being able to use the cluster, we recommend backing up the cluster, deleting it in Rancher, then restoring it from backup.
# Backing up Kubernetes Applications with Restic and Velero
Velero has support for backing up and restoring Kubernetes volumes using a free open-source backup tool called restic. This support is considered beta quality. Please see the list of limitations to understand if it currently fits your use case.
# Backing up Kubernetes Applications with Stash
Stash by AppsCode is a Kubernetes operator for restic. If you are running production workloads in Kubernetes, you might want to take backup of your disks. Traditional tools are too complex to setup and maintain in a dynamic compute environment like Kubernetes. restic is a backup program that is fast, efficient and secure with few moving parts. Stash is a CRD controller for Kubernetes built around restic to address these issues. Using Stash, you can backup Kubernetes volumes mounted in following types of workloads:
- Deployment
- DaemonSet
- ReplicaSet
- ReplicationController
- StatefulSet
content/rancher/v2.x/en/removing-rancher/_index.md
+6 -2
View File
@@ -10,6 +10,10 @@ aliases:
When you deploy the Rancher server, Rancher's components are installed on the nodes you use.
If you installed Rancher on a [high-availability]({{< baseurl >}}/rancher/v2.x/en/installation/ha/) Kubernetes cluster, remove Rancher by using the [System Tools]({{< baseurl >}}/rancher/v2.x/en/system-tools/) with the `remove` subcommand.
If you [installed Rancher on a Kubernetes cluster,]({{<baseurl>}}/rancher/v2.x/en/installation/ha/) remove Rancher by using the [System Tools]({{<baseurl>}}/rancher/v2.x/en/system-tools/) with the `remove` subcommand.
For information about how to remove Rancher components from downstream Kubernetes clusters, refer to the section on [detaching clusters.]({{<baseurl>}}/rancher/v2.x/en/detaching-rancher/)
### Detaching Rancher from Downstream Clusters
If an imported cluster is deleted from the Rancher UI, the cluster is detached from Rancher, but not destroyed. You can still access the cluster using `kubectl`.
For other types of clusters, including RKE clusters and hosted Kubernetes clusters, it is not possible to detach the cluster from Rancher in a way that allows you to continue using the cluster. If the cluster is deleted from the Rancher UI, it is destroyed.