Skip to content

Commit 4418965

Browse files
author
Katie Horne
authored
chore: update images and remove outdated info (coder#981)
1 parent 5ad1eb1 commit 4418965

File tree

4 files changed

+3
-23
lines changed

4 files changed

+3
-23
lines changed

assets/guides/admin/compute-5.png

35.3 KB
Loading

assets/guides/admin/compute-6.png

36.5 KB
Loading

assets/guides/admin/compute-7.png

34.3 KB
Loading

guides/admin/wp-cli.md

+3-23
Original file line numberDiff line numberDiff line change
@@ -48,29 +48,9 @@ description: Learn how to provision a workspace provider using the Coder CLI.
4848
coder providers create ec2 my-provider --access-key-id=AKIAIOSFODNN7EXAMPLE --secret-access-key=wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
4949
```
5050

51+
> Run `coder providers create <provider> --help` for a full list of options
52+
> available.
53+
5154
1. Once you've provisioned the workspace provider, deploy it to your
5255
[Kubernetes](../../admin/workspace-providers/deployment/kubernetes.md) or
5356
[EC2](../../admin/workspace-providers/deployment/ec2.md) cluster.
54-
55-
Ensure that you're connected to the cluster you're deploying to, and run the
56-
provided `helm upgrade` command; it should look something like the following,
57-
but with the placeholders filled with values appropriate to your deployment:
58-
59-
helm upgrade coder-workspace-provider coder/workspace-provider \
60-
--version=<version> \
61-
--atomic \
62-
--install \
63-
--force \
64-
--set envproxy.token=<token> \
65-
--set envproxy.accessURL=<envproxyAccessURL> \
66-
--set ingress.host=<ingressHostName> \
67-
--set envproxy.clusterAddress=<clusterAddress> \
68-
--set cemanager.accessURL=<cemanagerAccessUrl>
69-
70-
> WARNING: The 'envproxy.token' is a secret value that authenticates the
71-
> workspace provider; make sure that you don't share this token or make it
72-
> public.
73-
74-
You can set
75-
[additional values of the Helm Chart](https://github.com/cdr/enterprise-helm/blob/workspace-providers-envproxy-only/README.md)
76-
to customize the deployment further.

0 commit comments

Comments
 (0)