-
Notifications
You must be signed in to change notification settings - Fork 31
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
Conversation
✅ Deploy Preview for replicated-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for replicated-docs-upgrade ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
| * 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). |
There was a problem hiding this comment.
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
| 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_. |
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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} |
There was a problem hiding this comment.
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_. No newline at end of file |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we document some of the VM stuff now? If we do, why not refer to it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't quite yet--talking with Han about getting this in in the next couple weeks though
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or I'll amend that to say that we do have the replicated vm commands doc'd, but that's more just because those cli docs are automatically generated
| 'intro-replicated', | ||
| 'vendor/kots-faq', | ||
| 'vendor/quick-start', | ||
| 'vendor/environment-setup', |
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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
docs/vendor/environment-setup.mdx
Outdated
|
|
||
| ### Install sbctl | ||
|
|
||
| sbctl is a command-line tool that you can use to examine Kubernetes resources in support bundles. With sbctl, you can interact with the support bundle in a shell using kubectl commands to view and inspect resources. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"examine Kubernetes resources in support bundles" feels slightly off, though I'm not sure I have a better explanation…I usually explain it in the context of the support bundle having a snapshot of the state of the cluster, and sbctl letting you interact with that snapshot as if you had access to the cluster
Your explanation is clearer language and more direct, though I'm wondering if "Kubernetes resources in support bundles" doesn't imply something about the bundle that isn't accurate. There aren't actually any resources, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I usually explain it in the context of the support bundle having a snapshot of the state of the cluster, and sbctl letting you interact with that snapshot as if you had access to the cluster
I like that. I did struggle to explain this and agreed that I'm not sure "Kubernetes resources in support bundles" would necessarily make the most sense to people
| * [jq](https://jqlang.org/) for JSON processing | ||
| * [yq](https://mikefarah.gitbook.io/yq/) for YAML manipulation | ||
|
|
||
| These tools are useful when working with Kubernetes and Replicated configurations to reduce complex data manipulation tasks from multi-step processes into single commands, simplifying your development workflow. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
love this wording
|
|
||
| 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_. No newline at end of file |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we document some of the VM stuff now? If we do, why not refer to it.
|
|
||
| Embedded Cluster has the following 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_. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
don't you need to reference Helm here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this case "main onboarding tasks" refers to all the numbered tasks. Adding support for Helm is technically a "next step" after you onboard to Embedded Cluster.
I'm sure there's a more clear way for me to word that, though
https://deploy-preview-3351--replicated-docs.netlify.app/vendor/environment-setup