Add new topic on setting up your environment for replicated

Author: paigecalvert

docs/vendor/environment-setup.mdx

@@ -0,0 +1,122 @@
+import Requirements from "../partials/embedded-cluster/_requirements.mdx"
+
+# Set Up Your Environment
+
+This topic describes how to set up your environment to get started with the Replicated Platform. It includes information about installing the required tools on your local workstation as well as creating development environments for testing installation and upgrade scenarios for your application.
+
+## Set Up Your Local Workstation {#local}
+
+### Install kubectl
+
+Install kubectl, the Kubernetes command line tool.
+
+#### Mac
+
+Homebrew
+
+```
+brew install kubectl
+```
+
+You can also fetch kubectl using curl from the official Kubernetes release endpoint:
+
+```
+# macOS
+curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/darwin/amd64/kubectl"
+chmod +x ./kubectl
+sudo mv ./kubectl /usr/local/bin/kubectl
+```
+
+#### Linux
+
+Linux users have similar options, whether through package managers or direct downloads:
+
+```
+# Using curl
+curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl"
+chmod +x ./kubectl
+sudo mv ./kubectl /usr/local/bin/kubectl
+
+# Or using package manager (Ubuntu/Debian)
+sudo apt-get update
+sudo apt-get install -y kubectl
+
+# Or using package manager (CentOS/RHEL/Fedora)
+sudo yum install -y kubectl
+```
+
+### Install Helm
+
+Install the Helm CLI. 
+
+#### Mac
+
+Homebrew:
+
+```
+brew install helm
+```
+
+Or the official installation script that works across platforms:
+```
+curl https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | bash
+```
+#### Linux
+For manual installation on Linux:
+```
+curl -LO https://get.helm.sh/helm-v3.12.0-linux-amd64.tar.gz
+tar -zxvf helm-v3.12.0-linux-amd64.tar.gz
+sudo mv linux-amd64/helm /usr/local/bin/helm
+```
+
+###  Install the Replicated CLI
+
+The Replicated CLI serves as your primary interface to the platform.
+
+#### Mac
+On macOS, it’s available through a dedicated Homebrew tap:
+```
+brew install replicatedhq/replicated/cli
+```
+#### Linux
+Linux users can grab the latest release directly from GitHub:
+```
+curl -s https://api.github.com/repos/replicatedhq/replicated/releases/latest \
+| grep "browser_download_url.*linux_amd64.tar.gz" \
+| cut -d : -f 2,3 \
+| tr -d \" \
+| wget -O replicated.tar.gz -qi -
+
+tar xf replicated.tar.gz replicated && rm replicated.tar.gz
+sudo mv replicated /usr/local/bin/
+```
+
+### Authorize the Replicated CLI with your Replicated Account
+
+The `replicated login` command creates a token after you log in to your vendor account in a browser and saves it to a config file. 
+
+Authorize the Replicated CLI:
+
+replicated login
+
+In the browser window that opens, complete the prompts to log in to your vendor account and authorize the CLI.
+
+Alteratively, if you do not have access to a browser, you can set the REPLICATED_API_TOKEN environment variable to authenticate. For more information, see (Optional) Set Environment Variables.
+
+### Install the Preflight and Support Bundles CLIs
+
+## Set Up Development Environments for Testing {#dev}
+
+Testing your releases is an important part of the commercial software distribution lifecycle. Replicated recommends that you have access to a virtual machine (VM) and a cluster where you can deploy your releases for testing.
+
+### Create a VM
+
+Create a VM that you can use for testing installation with the Replicated Embedded Cluster installer. The VM must meet the following requirements:
+
+<Requirements/>
+
+### Create a Kubernetes Cluster
+
+Create a Kubernetes Cluster for testing Helm installations.
+
+You can use any cloud provider or tool that you prefer to create a cluster, such as [Replicated Compatibility Matrix](/vendor/testing-how-to), Google Kubernetes Engine (GKE), or minikube.

docs/vendor/replicated-onboarding.mdx

@@ -21,11 +21,9 @@ The following are some best practices and recommendations for successfully onboa
 
 * When integrating new Replicated features with an application, make changes in small iterations and test frequently by installing or upgrading the application in a development environment. This will help you to more easily identify issues and troubleshoot. This onboarding workflow will guide you through the process of integrating features in small iterations.
 
-* Use the Replicated CLI to create and manage your application and releases. Getting familiar with the Replicated CLI will also help later on when integrating Replicated workflows into your CI/CD pipelines. For more information, see [Install the Replicated CLI](/reference/replicated-cli-installing).
+* Use the Replicated CLI to create and manage your application and releases. Getting familiar with the Replicated CLI will also help later on when integrating Replicated workflows into your CI/CD pipelines.
 
-* These onboarding tasks assume that you will test the installation of each release on a VM with the Replicated Embedded Cluster installer _and_ in a cluster with the Replicated KOTS installer. If you do not intend to offer existing cluster installations with KOTS (for example, if you intend to support only Embedded Cluster and Helm installations for your users), then can choose to test with Embedded Cluster only.
-
-* Ask for help from the Replicated community. For more information, see [Get Help from the Community](#community) below.
+* These onboarding tasks show you how to test the installation of each release on a VM with the Replicated Embedded Cluster installer _and_ in a cluster with the Replicated KOTS installer. If you do not intend to offer existing cluster installations with KOTS, then can choose to test with Embedded Cluster only.
 
 ### Getting Help from the Community {#community}
 
@@ -35,23 +33,19 @@ Before posting in the community site, use the search to find existing knowledge
 
 To search and participate in the Replicated community, see https://community.replicated.com/.
 
-### Prerequisites
+## Prerequisites
 
 * Create an account in the Vendor Portal. You can either create a new team or join an existing team. For more information, see [Create a Vendor Account](vendor-portal-creating-account).
 
-* Install the Replicated CLI. See [Install the Replicated CLI](/reference/replicated-cli-installing).
-
-* Complete a basic quick start workflow to create an application with a sample Helm chart and then promote and install releases in a development environment. This helps you get familiar with the process of creating, installing, and updating releases in the Replicated Platform. See [Replicated Quick Start](/vendor/quick-start).
-
-* Ensure that you have access to a VM that meets the requirements for the Replicated Embedded Cluster installer. You will use this VM to test installation with Embedded Cluster.
+* Set up your local workstation with the required toolkit for working with the Replicated Platform. See [Set Up Your Local Workstation](/vendor/environment-setup#local).
 
-  Embedded Cluster has the following requirements:
+* Set up a VM. You will use this VM to test installation with the Replicated Embedded Cluster installer. See [Create a VM](/vendor/environment-setup#create-a-vm) in _Set Up Your Environment_.
 
-  <Requirements/>
+   :::note
+   You do not need access to a Kubernetes cluster for the main onboarding tasks, unless you intend to support existing cluster installations with Replicated KOTS. For information about how to create a cluster, see [Create a Kubernetes Cluster](/vendor/environment-setup#create-a-kubernetes-cluster) in _Set Up Your Environment_.
+   :::
 
-* (Optional) Ensure that you have kubectl access to a Kubernetes cluster. You will use this cluster to test installation with KOTS. If you do not intend to offer existing cluster installations with KOTS (for example, if you intend to support only Embedded Cluster and Helm installations for your users), then you do not need access to a cluster for the main onboarding tasks.
-
-  You can use any cloud provider or tool that you prefer to create a cluster, such as [Replicated Compatibility Matrix](/vendor/testing-how-to), Google Kubernetes Engine (GKE), or minikube. 
+* Complete a basic quick start workflow to create an application with a sample Helm chart and then promote and install releases in a development environment. This helps you get familiar with the process of creating, installing, and updating releases in the Replicated Platform. See [Replicated Quick Start](/vendor/quick-start).
 
 ## Onboard
 
@@ -416,7 +410,7 @@ After completing the main onboarding tasks, Replicated recommends that you also
 
 ### Add Support for Helm Installations
 
-Existing KOTS releases that include one or more Helm charts can be installed with the Helm CLI; it is not necessary to create and manage separate releases or channels for each installation method.
+Existing releases that include one or more Helm charts can be installed with the Helm CLI; it is not necessary to create and manage separate releases or channels for each installation method.
 
 To enable Helm installations for Helm charts distributed with Replicated, the only extra step is to add a Secret to your chart to authenticate with the Replicated proxy registry.  
 
@@ -436,7 +430,9 @@ To support and test Helm installations:
 
 1. Add the `.tgz` file to a release. For more information, see [Manage Releases with the Vendor Portal](releases-creating-releases) or [Managing Releases with the CLI](releases-creating-cli).
 
-1. Install the release in a cluster with the Helm CLI to test your changes. For more information, see [Install with Helm](/vendor/install-with-helm).
+1. Create or get kubectl access to a cluster to test the installation. See [Create a Kubernetes Cluster](/vendor/environment-setup#create-a-kubernetes-cluster) in _Set Up Your Environment_.
+
+1. In the cluster, istall the release with Helm to test your changes. For more information, see [Install with Helm](/vendor/install-with-helm).
 
 ### Add Support for Air Gap Installations
 

sidebars.js

@@ -38,6 +38,7 @@ const sidebars = {
     'intro-replicated',
     'vendor/kots-faq',
     'vendor/quick-start',
+    'vendor/environment-setup',
     'vendor/replicated-onboarding',
     // {
     //   type: 'category',