WAIT FOR EC GA: Onboarding docs updates #2528
Conversation
replicated-ci
added
type::docs
❌ Deploy Preview for replicated-docs-upgrade failed. Why did it fail? →
|
❌ Deploy Preview for replicated-docs failed. Why did it fail? →
|
|
|
||
|  | ||
|
|
||
| [View a larger version of this image](/images/quick-start-ec-slack-preflight.png) |
There was a problem hiding this comment.
^ Not sure why, but one of the times that I did this quick start workflow, the update never finished. The status just sort of hung as Updating. Curious if that happens for anyone else
|
|
||
| 1. In the Admin Console, go to the **Version history** tab. | ||
|
|
||
| 1. Click **Check for update**. |
There was a problem hiding this comment.
^ For me, the new version that pops up has the same version label as the previous version. Not sure if there's something different I should be doing so this number increments (or if that matters)
docs/vendor/quick-start-helm.mdx
Outdated
| import Preflights from "../partials/getting-started/_quick-start-preflights.mdx" | ||
| import InstanceInsights from "../partials/getting-started/_quick-start-instance-insights.mdx" | ||
|
|
||
| # Helm-Only Quick Start |
There was a problem hiding this comment.
This is pretty much the same as the existing quick start in the docs, but I did run through it a few times and made some updates (main edit was to have people use the replicated cli rather than the vendor portal to create the release)
docs/vendor/quick-start-helm.mdx
Outdated
| kubectl get svc gitea --watch | ||
| ``` | ||
|
|
||
| 1. After an external IP address is available for the `gitea` LoadBalancer service, confirm that you can open the application in a browser by going to `http://SERVICE_IP`, where `SERVICE_IP` is the external IP address for the `gitea` LoadBalancer service. |
There was a problem hiding this comment.
^ the output of the helm install command for Gitea provides instructions for creating the url where you can access the app. When I copy and pasted the commands provided, for some reason it was appending "VIP" to the end of the external IP in the url, which broke the link. This is the first time I've had this happen, but just to be safe this step explains how to create the URL rather than telling people to follow the instrux in the install command
paigecalvert
changed the title
| import Intro from "../partials/getting-started/_onboard-intro.mdx" | ||
| import UpdateChecks from "../partials/getting-started/_sdk-api-update-checks.mdx" | ||
|
|
||
| # Embedded Cluster Onboarding |
There was a problem hiding this comment.
This is the new Embedded Cluster onboarding topic. It assumes starting from zero (after completing the quick start).
|
Closing this PR in favor of #2678 This PR got out of date with the rest of the site. Additionally, we no longer want to provide a Helm-only path. |
KOTS/EC Quick start: https://deploy-preview-2528--replicated-docs-upgrade.netlify.app/vendor/quick-start-embedded
Helm only quick start: https://deploy-preview-2528--replicated-docs-upgrade.netlify.app/vendor/quick-start-helmKOTS/EC onboarding: https://deploy-preview-2528--replicated-docs-upgrade.netlify.app/vendor/distributing-workflow
Helm only onboarding: https://deploy-preview-2528--replicated-docs-upgrade.netlify.app/vendor/replicated-onboarding