Skip to content

Add new topic on setting up your environment for replicated #3351

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

paigecalvert
Copy link
Contributor

@paigecalvert paigecalvert commented Jul 1, 2025

Copy link

netlify bot commented Jul 1, 2025

Deploy Preview for replicated-docs ready!

Name Link
🔨 Latest commit 26e17fb
🔍 Latest deploy log https://app.netlify.com/projects/replicated-docs/deploys/6866b16f3b435b00089ff551
😎 Deploy Preview https://deploy-preview-3351--replicated-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@replicated-ci replicated-ci added type::docs Improvements or additions to documentation type::feature labels Jul 1, 2025
Copy link

netlify bot commented Jul 1, 2025

Deploy Preview for replicated-docs-upgrade ready!

Name Link
🔨 Latest commit 26e17fb
🔍 Latest deploy log https://app.netlify.com/projects/replicated-docs-upgrade/deploys/6866b16f48cb510008aaa3e9
😎 Deploy Preview https://deploy-preview-3351--replicated-docs-upgrade.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@paigecalvert paigecalvert marked this pull request as ready for review July 2, 2025 21:44
@paigecalvert paigecalvert requested a review from a team as a code owner July 2, 2025 21:44
@@ -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).
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

^ removed this xref because I added a new link to the "Set Up Your Environment" page in the prerequisites

* 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).
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

^ link to the new Set Up Your Environment topic in the prerequisites for onboarding

@@ -436,7 +434,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_.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

^ This is the Add Support for Helm Installations subsection. Previously, we didn't explicitly tell people that they needed a cluster for testing

import Logout from "../partials/replicated-cli/_logout.mdx"
import AuthToken from "../partials/replicated-cli/_authorize-with-token-note.mdx"

# Set Up Your Environment
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

New topic with information from https://community.replicated.com/t/setting-up-your-system-for-working-with-the-replicated-platform/1528 about how to set up you local workstation, and about creating VMs/clusters for testing releases.

I used partials to share some preexisting content between pages. For example, the steps on installing the Replicated CLI are shared between this topic and https://docs.replicated.com/reference/replicated-cli-installing


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}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Split this up in two main sections:

  • Set up local workstation
  • Set up dev environments for testing

I wanted to explicitly make this distinction because I think there's some confusion with new onboarders around what gets installed locally versus in a dev/"sample customer" environment


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.

For information about how to create a cluster with Compatibility Matrix, see [Prerequisites](/vendor/testing-how-to#prerequisites) and [Create Clusters](/vendor/testing-how-to#create-clusters) in _Use Compatibility Matrix_.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will be nice in the future when you can create VMs and air gap environments with CMX to include those here too

@@ -38,6 +38,7 @@ const sidebars = {
'intro-replicated',
'vendor/kots-faq',
'vendor/quick-start',
'vendor/environment-setup',
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added to Get Started section of sidebar

sudo mv linux-amd64/helm /usr/local/bin/helm
```

### Install and Authorize the Replicated CLI
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Most of this was existing content from the Install the Replicated CLI topic. I like that it already included the info about how to authorize the cli with the login command or with env vars

I also updated this to include your WSL2 recommendation for windows

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type::docs Improvements or additions to documentation type::feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants