@@ -69,7 +69,7 @@ container runtime, but here is a partial list to help you get started:
69
69
If the cluster uses containerd, apply the following to patch in certificates for
70
70
images in the local registry domain:
71
71
72
- ``` console
72
+ ``` bash
73
73
update-ca-certificates
74
74
cat << EOT >> /etc/containerd/config.toml
75
75
[plugins."io.containerd.grpc.v1.cri".registry.configs."$REGISTRY_DOMAIN_NAME ".tls]
@@ -99,7 +99,7 @@ To pass a self-signed certificate to Coder's images, you'll need to:
99
99
100
100
To create a secret, run:
101
101
102
- ``` console
102
+ ``` bash
103
103
kubectl -n coder create secret generic local-registry-cert --from-file=/certs
104
104
```
105
105
@@ -113,7 +113,7 @@ becomes the secret **key**.
113
113
114
114
To verify the new secret:
115
115
116
- ``` console
116
+ ``` bash
117
117
kubectl -n coder get secret local-registry-cert -o yaml
118
118
```
119
119
@@ -130,7 +130,7 @@ certs:
130
130
Then, add the flag ` -f registry-cert-values.yml` to the end of the `helm install`
131
131
or `helm upgrade` command to include the new secrets file :
132
132
133
- ` ` ` console
133
+ ` ` ` bash
134
134
helm install --wait --atomic --debug --namespace coder coder . \
135
135
--set cemanager.image=$REGISTRY_DOMAIN_NAME/coderenvs/coder-service:<version> \
136
136
--set envproxy.image=$REGISTRY_DOMAIN_NAME/coderenvs/coder-service:<version> \
@@ -147,7 +147,7 @@ registry's static IP address. One way to do this without an external DNS server
147
147
is to use the node's hosts file. For example, if the registry is on 10.0.0.2,
148
148
then add this to the Node configuration script :
149
149
150
- ` ` ` console
150
+ ` ` ` bash
151
151
echo "10.0.0.2 $REGISTRY_DOMAIN_NAME" >> /etc/hosts
152
152
` ` `
153
153
0 commit comments