Remove standalone cluster doc.

Signed-off-by: kcoriordan <[email protected]>

change title

Signed-off-by: kcoriordan <[email protected]>

addons/packages/grafana/7.5.7/README.md

@@ -20,7 +20,7 @@ The following table shows the providers this package can work with.
 
 The following configuration values can be set to customize the Grafana installation.
 
-> Note: Ingress for Grafana server is enabled by default, and can be disabled using the `ingress.enabled`configuration field. For standalone clusters running in Docker, disabling the Ingress is the easiest way to get started, as setting up Contour on a Docker cluster requires additional configuration.
+> Note: Ingress for Grafana server is enabled by default, and can be disabled using the `ingress.enabled` configuration field. For clusters running in Docker, disabling the Ingress is the easiest way to get started, as setting up Contour on a Docker cluster requires additional configuration.
 > If you choose to enable the Contour-based Ingress, Contour must also be installed on the target cluster. Additionally, enabling the Ingress requires either cert-manager or your own user-provided TLS certificate (`ingress.tlsCertificate.tls.crt` and `ingress.tlsCertificate.tls.key`) to configure TLS settings for the Ingress. For ad-hoc Grafana UI access without an Ingress, use kubectl port-forward.
 
 | Parameter                                          | Description                                                                                                                       | Type        | Default                                    |

docs/site/content/docs/assets/aws-clusters.md

@@ -3,7 +3,7 @@
 This section describes setting up management and workload clusters in Amazon Web
 Services (AWS).
 
-There are some prerequisites the installation process will assume.  Refer to the [Prepare to Deploy a Management or Standalone Cluster to AWS](../aws) docs for instructions on deploying an SSH key-pair and preparing your AWS account.
+There are some prerequisites the installation process will assume.  Refer to the [Prepare to Deploy a Management Cluster to AWS](../aws) docs for instructions on deploying an SSH key-pair and preparing your AWS account.
 
 1. Initialize the Tanzu Community Edition installer interface.
 

docs/site/content/docs/assets/capd-clusters-windows.md

@@ -29,7 +29,7 @@ This behavior will eventually be addressed in
 1. Create the management cluster.
 
     ```sh
-    CLUSTER_PLAN=dev tanzu management-cluster create -i docker <STANDALONE-CLUSTER-NAME>
+    CLUSTER_PLAN=dev tanzu management-cluster create -i docker <MANAGEMENT-CLUSTER-NAME>
     ```
 
     > For increased logs, you can append `-v 10`.

docs/site/content/docs/assets/metadata.md

@@ -5,4 +5,4 @@ In the optional **Metadata** section, provide descriptive information about the
 - **Labels**: Key/value pairs to help users identify clusters, for example `release : beta`, `environment : staging`, or `environment : production`. For more information, see [Labels and Selectors](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/).<br />
 You can click **Add** to apply multiple labels to the clusters.
 
-Any metadata that you specify here applies to the management cluster, standalone clusters, and workload clusters, and can be accessed by using the cluster management tool of your choice.
+Any metadata that you specify here applies to the management cluster and workload clusters, and can be accessed by using the cluster management tool of your choice.

docs/site/content/docs/assets/package-installation.md

@@ -8,26 +8,23 @@ For detailed instruction on package management, see [Work with Packages](../pack
 
 ### Prerequisites
 
-- Before you install packages, you should have one of the following cluster configurations running:
+- Before you install packages, you should have the following cluster configurations running:
 
   - A [management cluster](https://tanzucommunityedition.io/docs/latest/glossary/#management-cluster) and a [workload cluster](https://tanzucommunityedition.io/docs/latest/glossary/#workload-cluster).
 
-    **or**
-
-  - A [standalone cluster](https://tanzucommunityedition.io/docs/latest/glossary/#standalone-cluster)
-- If you deployed a management/workload cluster, you will install cert-manager in the workload cluster. If you deployed a standalone cluster, you will install cert-manager in the standalone cluster.
+<!--Add note here about unmanaged cluster when it is available-->
 
 For more information, see [Planning Your Installation](https://tanzucommunityedition.io/docs/latest/installation-planning/).
 
 ### Procedure
 
-1. Make sure your `kubectl` context is set to either the workload cluster or standalone cluster.
+1. Make sure your `kubectl` context is set to the workload cluster.
 
     ```sh
     kubectl config use-context <CLUSTER-NAME>-admin@<CLUSTER-NAME>
     ```
 
-    Where ``<CLUSTER-NAME>`` is the name of workload or standalone cluster where you want to install a package.
+    Where ``<CLUSTER-NAME>`` is the name of the workload where you want to install a package.
 
 1. Install the Tanzu Community Edition package repository into the `tanzu-package-repo-global` namespace.
 

docs/site/content/docs/assets/prereq-linux.md

@@ -4,7 +4,7 @@
 |Arch: x86; ARM is currently unsupported|
 |RAM: 6 GB|
 |CPU: 2|
-|[Docker](https://docs.docker.com/engine/install/) <BR> Add your non-root user account to the docker user group. Create the group if it does not already exist. This lets the Tanzu CLI access the Docker socket, which is owned by the root user. For more information, see steps 1 to 4 in the [Manage Docker as a non-root user](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) procedure in the Docker documentation.|
+|[Docker](https://docs.docker.com/engine/install/) <BR> In Docker, you must create the docker group and add your user before you attempt to create a management cluster. Complete steps 1 to 4 in the [Manage Docker as a non-root user](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user) procedure in the Docker documentation.|
 |[Kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/) |
 |Latest version of Chrome, Firefox, Safari, Internet Explorer, or  Edge|
 |System time is synchronized with a Network Time Protocol (NTP) server.|

docs/site/content/docs/assets/unmanaged-cluster-note.md

@@ -0,0 +1 @@
+**Note**: The following information relates to a management/workload cluster deployment which provides a full-featured, scalable Kubernetes implementation suitable for a development or production environment. If you are interested in quickly spinning up a lightweight cluster for a development/experimental environment, see [Getting Started with Unmanaged Clusters](../getting-started-unmanaged).

docs/site/content/docs/latest/architecture.md

@@ -6,7 +6,6 @@ services ran atop. This page details the architecture of:
 
 * Tanzu CLI
 * Managed Clusters
-* Standalone Clusters
 * Package Management
 
 ## Tanzu CLI
@@ -101,41 +100,6 @@ relationship end-to-end.
 
 ![Management cluster bootstrapping](../../img/management-cluster-flow.png)
 
-## Standalone Clusters
-
-Clusters that run without a long-running management cluster are considered
-standalone clusters. This is an experimental cluster deployment model currently
-being iterated on by the Tanzu Community Edition team. This model provides a few
-benefits including:
-
-* Faster time to cluster (relative to managed clusters)
-* Reduced system requirements
-
-Experiments and new development are actively being run to achieve the above. As
-such, this is not a recommended deployment model for production workloads.
-
-Creating a standalone cluster is done using the `tanzu standalone-cluster
-create` command. When running this command, a bootstrap cluster is created
-locally and is then used to create the standalone cluster. After successful
-bootstrapping, the bootstrap cluster is deleted. Management resources are
-**not** moved into the standalone cluster. This newly created cluster can be
-referred to as a workload cluster.  The following diagram shows this
-relationship.
-
-![Standalone cluster flow](../../img/standalone-cluster-flow.png)
-
-When you'd like to delete or scale the workload cluster, a new bootstrap
-cluster is created and the workload cluster is deleted or scaled. This bootstrap
-cluster can be thought of as a _temporary_ management cluster. Users should
-expect a delay in the operation as there will be time lost to re-creating the
-boostrap cluster. The following diagram shows this relationship.
-
-![Standalone scale example flow](../../img/flow-for-standalone-mutation.png)
-
-Standalone clusters are implemented using a similar code path to that of
-management-clusters. However, we short-circuit the cluster creation to not fully
-"pivot" the newly created cluster into something that manages other clusters.
-
 ## Package Management
 
 Tanzu Community Edition provides package management to users via the `tanzu`

docs/site/content/docs/latest/aws-install-mgmt.md

@@ -6,10 +6,10 @@
 
 1. In the **IaaS Provider** section, enter credentials for your AWS account. You have two options:
    * In the **AWS Credential Profile** drop-down, you can select an already existing AWS credential profile. If you select a profile, the access key and session token information configured for your profile are passed to the Installer without displaying actual values in the UI.
-   * Alternately, enter AWS account credentials directly in the **Access Key ID** and **Secret Access Key** fields for your AWS account. For information about setting up credential profiles, see [Prepare to Deploy a Management or Standalone Cluster to AWS](aws).
+   * Alternately, enter AWS account credentials directly in the **Access Key ID** and **Secret Access Key** fields for your AWS account. For information about setting up credential profiles, see [Prepare to Deploy a Management Cluster to AWS](aws).
    * Optionally, specify an AWS session token in **Session Token** if your AWS account is configured to require temporary credentials. For more information on acquiring session tokens, see [Using temporary credentials with AWS resources](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_temp_use-resources.html).
 1. In **Region**, select the AWS region in which to deploy the cluster. If you intend to deploy a production management cluster, this region must have at least three availability zones. This region must also be registered with the SSH key entered in the next field.  A list of regions is available [here](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html#concepts-available-regions) in the AWS documentation.
-1. In **SSH Key Name**, specify the name of an SSH key that is already registered with both your Amazon EC2 account and the region where you are deploying the cluster. For information about setting up credential profiles, see [Prepare to Deploy a Management or Standalone Cluster to AWS](aws).
+1. In **SSH Key Name**, specify the name of an SSH key that is already registered with both your Amazon EC2 account and the region where you are deploying the cluster. For information about setting up credential profiles, see [Prepare to Deploy a Management Cluster to AWS](aws).
 1. If this is the first time deploying a cluster, select the **Automate creation of AWS CloudFormation Stack** checkbox, and click **Connect**.
 
    The CloudFormation stack creates the identity and access management (IAM) resources that Tanzu Community Edition needs to deploy and run clusters on AWS. For more information, see [Required IAM Resources](ref-aws.md#permissions).

docs/site/content/docs/latest/aws-intro.md

@@ -12,8 +12,6 @@ Complete the following steps for a full Tanzu Community Edition implementation t
 
 1. [Deploy a workload cluster](workload-clusters)
 
-1. (Alternative)[Deploy a standalone cluster](aws-install-standalone)
-
 1. [Examine the cluster](verify-deployment)
 
 1. [Work with Packages](package-management)

docs/site/content/docs/latest/aws.md

@@ -1,8 +1,8 @@
-# Prepare to Deploy a Management or Standalone Cluster to AWS
+# Prepare to Deploy a Management Cluster to AWS
 
-This topic explains how to prepare your environment before you deploy a management or standalone cluster to Amazon Web Services (AWS).
+This topic explains how to prepare your environment before you deploy a management cluster to Amazon Web Services (AWS).
 
-To enable Tanzu Community Edition VMs to launch on Amazon EC2, you must configure your AWS account credentials and then provide the public key part of an SSH key pair to Amazon EC2 for every region in which you plan to deploy a management or standalone cluster.
+To enable Tanzu Community Edition VMs to launch on Amazon EC2, you must configure your AWS account credentials and then provide the public key part of an SSH key pair to Amazon EC2 for every region in which you plan to deploy a management cluster.
 
 ## Before you begin
 

docs/site/content/docs/latest/azure-intro.md

@@ -12,8 +12,6 @@ Complete the following steps for a full Tanzu Community Edition implementation t
 
 1. [Deploy a workload cluster](workload-clusters)
 
-1. (Alternative)[Deploy a standalone cluster](azure-install-standalone)
-
 1. [Examine the cluster](verify-deployment)
 
 1. [Work with Packages](package-management)

docs/site/content/docs/latest/azure-mgmt.md

@@ -1,6 +1,6 @@
 # Preparing to Deploy Clusters to Microsoft Azure
 
-This topic explains how to prepare your environment before you deploy a management or standalone cluster on Microsoft Azure.
+This topic explains how to prepare your environment before you deploy a management cluster on Microsoft Azure.
 
 <!--If you are installing Tanzu Community Edition on Azure VMware Solution (AVS), you are installing to a vSphere environment.
 See [Preparing Azure VMware Solution on Microsoft Azure](prepare-maas.md#prep-avs) in _Prepare a vSphere Management as a Service Infrastructure_ to prepare your environment

docs/site/content/docs/latest/cli-installation.md

@@ -4,6 +4,8 @@ Tanzu Community Edition consists of the Tanzu CLI and a select set of plugins. Y
 
 Installing the Tanzu Community Edition extracts the binaries and configures the plugin repositories. The first time you run the `tanzu` command the installed plugins and plugin repositories are initialized. This action might take a minute.
 
+{{% include "/docs/assets/unmanaged-cluster-note.md" %}}
+
 ## Procedure
 
 {{< tabs tabTotal="3" tabID="1" tabName1="Linux" tabName2="Mac" tabName3="Windows">}}

docs/site/content/docs/latest/contribute/style-guide.md

@@ -268,7 +268,6 @@ A list of specific terms and words to be used consistently across the site.
 |Allowlist|Use allowlist instead of whitelist.|
 |Denylist|Use denylist instead of blacklist.|
 |Workload cluster|Use workload cluster instead of guest cluster.|
-|Standalone|Use standalone instead of stand alone, stand-alone, or SC.|
 |Bookstrap machine|Use bootstrap machine instead of boot-strap machine.|
 |Tanzu Community Edition installer interface on first occurrence and installer interface on subsequent occurrences|Use installer ui, installer, kickstart ui. |
 {{< /table >}}

docs/site/content/docs/latest/docker-intro.md

@@ -8,8 +8,6 @@ Complete the following steps for a full Tanzu Community Edition implementation t
 
 1. [Deploy management and workload clusters](docker-install-mgmt)
 
-1. (Alternative)[Deploy a standalone cluster](docker-install-standalone)
-
 1. [Examine the cluster](verify-deployment)
 
 1. [Work with Packages](package-management)