From abd7e860441ccdfdff6652899b78bff2138f3a83 Mon Sep 17 00:00:00 2001 From: Katie Horne Date: Mon, 22 Mar 2021 15:43:14 -0500 Subject: [PATCH 1/2] Fix link to helm charts --- admin/workspace-providers/deployment.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/admin/workspace-providers/deployment.md b/admin/workspace-providers/deployment.md index 07910d259..35443dd81 100644 --- a/admin/workspace-providers/deployment.md +++ b/admin/workspace-providers/deployment.md @@ -124,9 +124,9 @@ when communicating with the Coder deployment. For installations using HTTPS, you must [ensure the deployment has a valid certificate](../../guides/ssl-certificates/index.md). If you're unfamiliar with the helm configuration values file, see our doc on - [updating a helm chart](../../guides/helm-charts.md) + [updating a helm chart](../../guides/admin/helm-charts.md) -1. Once the helm chart is successfully deployed, fetch the ingress address: +2. Once the helm chart is successfully deployed, fetch the ingress address: ```bash kubectl get ingress web-ingress @@ -135,12 +135,12 @@ when communicating with the Coder deployment. Use this IP to create a DNS record for the provided hostname of the workspace provider. -1. Once the Helm chart has deployed successfully, you should see the workspace +3. Once the Helm chart has deployed successfully, you should see the workspace provider in a `ready` state on the Workspace Provider Admin page. ![Workspace Providers Admin](../../assets/workspace-providers-admin.png) -1. From the Workspace Provider Admin page, add the desired organizations to its +4. From the Workspace Provider Admin page, add the desired organizations to its allowlist. Users in the allowed organizations can now choose to deploy into the newly set From 50ee2a67d574f194d99d35f6ee452dfb66ea5744 Mon Sep 17 00:00:00 2001 From: Katie Horne Date: Mon, 22 Mar 2021 15:45:59 -0500 Subject: [PATCH 2/2] Undo auto-numbering --- admin/workspace-providers/deployment.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/admin/workspace-providers/deployment.md b/admin/workspace-providers/deployment.md index 35443dd81..e8a5d0590 100644 --- a/admin/workspace-providers/deployment.md +++ b/admin/workspace-providers/deployment.md @@ -126,7 +126,7 @@ when communicating with the Coder deployment. If you're unfamiliar with the helm configuration values file, see our doc on [updating a helm chart](../../guides/admin/helm-charts.md) -2. Once the helm chart is successfully deployed, fetch the ingress address: +1. Once the helm chart is successfully deployed, fetch the ingress address: ```bash kubectl get ingress web-ingress @@ -135,12 +135,12 @@ when communicating with the Coder deployment. Use this IP to create a DNS record for the provided hostname of the workspace provider. -3. Once the Helm chart has deployed successfully, you should see the workspace +1. Once the Helm chart has deployed successfully, you should see the workspace provider in a `ready` state on the Workspace Provider Admin page. ![Workspace Providers Admin](../../assets/workspace-providers-admin.png) -4. From the Workspace Provider Admin page, add the desired organizations to its +1. From the Workspace Provider Admin page, add the desired organizations to its allowlist. Users in the allowed organizations can now choose to deploy into the newly set