Merge pull request #2846 from replicatedhq/116159

Snapshots only for KOTS existing and kURL

Author: paigecalvert

docs/enterprise/snapshots-understanding.mdx

@@ -3,10 +3,15 @@ import Dr from "../partials/snapshots/_limitation-dr.mdx"
 import Os from "../partials/snapshots/_limitation-os.mdx"
 import InstallMethod from "../partials/snapshots/_limitation-install-method.mdx"
 import CliRestores from "../partials/snapshots/_limitation-cli-restores.mdx"
+import NoEcSupport from "../partials/snapshots/_limitation-no-ec-support.mdx"
 
-# About Backup and Restore
+# About Backing Up and Restoring with Snapshots
 
-This topic provides an introduction to the Replicated KOTS snapshots feature, including information about backing up and restoring KOTS installations with snapshots. 
+This topic provides an introduction to performing backup and restore with the Replicated KOTS snapshots feature. 
+
+:::note
+<NoEcSupport/>
+:::
 
 ## Overview
 
@@ -16,7 +21,9 @@ Velero and restic are the underlying technologies for snapshots. For more inform
 
 ### Limitations and Considerations
 
-- The snapshots feature is available only for KOTS-enabled licenses with the **Allow Snapshots** feature.
+* <NoEcSupport/>
+
+- The snapshots feature is available only for licenses with the **Allow Snapshots** option enabled. For more information, see [Creating and Managing Customers](/vendor/releases-creating-customer).
 
 - Snapshots are useful for rollback and disaster recovery scenarios. They are not intended to be used for application migration.
 

docs/partials/snapshots/_limitation-no-ec-support.mdx

@@ -0,0 +1 @@
+The KOTS Snapshots feature is supported for existing cluster installations with KOTS and Replicated kURL installations only. Snapshots is not supported for Replicated Embedded Cluster installations. For more information about configuring backup and restore for Embedded Cluster, see [Disaster Recovery for Embedded Cluster](/vendor/embedded-disaster-recovery).

docs/vendor/packaging-rbac.md

@@ -4,7 +4,7 @@ This topic describes role-based access control (RBAC) for Replicated KOTS in exi
 
 ## Cluster-scoped RBAC
 
-When a user installs your application in an existing cluster, Kubernetes RBAC resources are created to allow KOTS to install and manage the application.
+When a user installs your application with KOTS in an existing cluster, Kubernetes RBAC resources are created to allow KOTS to install and manage the application.
 
 By default, the following ClusterRole and ClusterRoleBinding resources are created that grant KOTS access to all resources across all namespaces in the cluster:
 
@@ -98,11 +98,11 @@ The following limitations apply when using the `requireMinimalRBACPrivileges` or
 
 * **Preflight checks**: When namespace-scoped access is enabled, preflight checks cannot read resources outside the namespace where KOTS is installed. The preflight checks continue to function, but return less data. For more information, see [Defining Preflight Checks](/vendor/preflight-defining).
 
-* **Velero namespace access**: Namespace-scoped RBAC does not grant access to the namespace where Velero is installed in the cluster. Velero is a requirement for configuring backup and restore with snapshots. 
+* **Velero namespace access for KOTS snapshots**: Velero is required for enabling backup and restore with the KOTS snapshots feature. Namespace-scoped RBAC does not grant access to the namespace where Velero is installed in the cluster. 
 
    To set up snapshots when KOTS has namespace-scoped access, users can run the `kubectl kots velero ensure-permissions` command. This command creates additional Roles and RoleBindings to allow the necessary cross-namespace access. For more information, see [`velero ensure-permissions`](/reference/kots-cli-velero-ensure-permissions/) in the KOTS CLI documentation.
 
-   For more information about snapshots, see [About Backup and Restore](/enterprise/snapshots-understanding).
+   For more information about snapshots, see [About Backing Up and Restoring with Snapshots](/enterprise/snapshots-understanding).
 
 * **Air Gap Installations**: For air gap installations, the `requireMinimalRBACPrivileges` and `supportMinimalRBACPrivileges` flags are supported only in automated, or _headless_, installations. In headless installations, the user passes all the required information to install both KOTS and the application with the `kots install` command. In non-headless installations, the user provides information to install the application through the Admin Console UI after KOTS is installed.
 

docs/vendor/snapshots-overview.md

@@ -1,12 +1,17 @@
 import RestoreTable from "../partials/snapshots/_restoreTable.mdx"
+import NoEcSupport from "../partials/snapshots/_limitation-no-ec-support.mdx"
 
 # Understanding Backup and Restore
 
-This topic describes how vendors enable the backup and restore feature, the type of data that is backed up, and how to troubleshoot issues for enterprise users. 
+This topic provides an introduction to the Replicated KOTS snapshots feature for backup and restore. It describes how vendors enable snapshots, the type of data that is backed up, and how to troubleshoot issues for enterprise users.
+
+:::note
+<NoEcSupport/>
+:::
 
 ## About Backup and Restore
 
-As a vendor, when you distribute your application with Replicated KOTS you can enable Replicated snapshots to support backup and restore for your enterprise users.
+You can enable Replicated KOTS snapshots to support backup and restore for existing cluster installations with KOTS and Replicated kURL installations.
 
 Snapshots uses the Velero open source project as the backend to back up Kubernetes manifests and persistent volumes. Velero is a mature, fully-featured application. For more information, see the [Velero documentation](https://velero.io/docs/).
 
@@ -16,7 +21,7 @@ KOTS provides the Admin Console and the KOTS CLI so that your users can fully ma
 
 ## What Data is Backed Up
 
-Full backups include the Admin Console and all application data, including KOTS-specific object-stored data. For embedded clusters created with Replicated kURL, this also backs up the Docker registry, which is required for air gapped installations.
+Full backups include the Admin Console and all application data, including KOTS-specific object-stored data. For Replicated kURL installations, this also backs up the Docker registry, which is required for air gapped installations.
 
 ### Other Object-Stored Data
 
@@ -41,7 +46,7 @@ To enable the snapshots backup and restore feature for your users, you must:
 
 ## Understanding Backup and Restore for Enterprise Users {#how-users}
 
-After vendors enable backup and restore, enterprise users install Velero and configure a storage destination in the Admin Console. Then users can create backups manually or schedule automatic backups. For more information about how users create and restore backups, see [About Backup and Restore](/enterprise/snapshots-understanding) in _Enterprise_.
+After vendors enable backup and restore, enterprise users install Velero and configure a storage destination in the Admin Console. Then users can create backups manually or schedule automatic backups. For more information about how users create and restore backups, see [About Backing Up and Restoring with Snapshots](/enterprise/snapshots-understanding).
 
 Replicated recommends advising your users to make full backups for disaster recovery purposes. Additionally, full backups give users the flexibility to do a full restore, a partial restore (application only), or restore just the Admin Console.
 
@@ -55,8 +60,8 @@ Partial backups are not recommended as they are a legacy feature and only back u
 
 To support end users with backup and restore, use the following resources:
 
-- To help troubleshoot error messages, see [Troubleshooting Backup and Restore](/enterprise/snapshots-troubleshooting-backup-restore) in _Enterprise_. 
+- To help troubleshoot error messages, see [Troubleshooting Backup and Restore](/enterprise/snapshots-troubleshooting-backup-restore). 
 
-- Review the Limitations and Considerations section to make sure an end users system is compliant. See [Limitations and Considerations](/enterprise/snapshots-understanding#limitations-and-considerations) in _Enterprise_.
+- Review the Limitations and Considerations section to make sure an end users system is compliant. See [Limitations and Considerations](/enterprise/snapshots-understanding#limitations-and-considerations).
 
-- Check that the installed Velero version and KOTS version are compatible. See [Velero Version Compatibility](/enterprise/snapshots-understanding#velero-version-compatibility) in _Enterprise_.
+- Check that the installed Velero version and KOTS version are compatible. See [Velero Version Compatibility](/enterprise/snapshots-understanding#velero-version-compatibility).