File tree 4 files changed +3
-23
lines changed
4 files changed +3
-23
lines changed Original file line number Diff line number Diff line change @@ -48,29 +48,9 @@ description: Learn how to provision a workspace provider using the Coder CLI.
48
48
coder providers create ec2 my-provider --access-key-id=AKIAIOSFODNN7EXAMPLE --secret-access-key=wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
49
49
```
50
50
51
+ > Run ` coder providers create <provider> --help ` for a full list of options
52
+ > available.
53
+
51
54
1 . Once you've provisioned the workspace provider, deploy it to your
52
55
[ Kubernetes] ( ../../admin/workspace-providers/deployment/kubernetes.md ) or
53
56
[ 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.
You can’t perform that action at this time.
0 commit comments