You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/vendor/replicated-sdk-customizing.md
+20-1Lines changed: 20 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -246,4 +246,23 @@ replicated:
246
246
podLabels:
247
247
monitoring: enabled
248
248
custom.company.io/pod-label: value
249
-
```
249
+
```
250
+
251
+
## Enable SSL
252
+
253
+
With the Replicated SDK version 1.6.0 and later, you can serve traffic from the Replicated SDK pod by setting the `replicated.tlsCertSecretName` Helm value in your Helm chart.
254
+
255
+
To configure the Replicated SDK pod to serve traffic over SSL:
256
+
257
+
1. Ensure a secret exists in the namespace with keys `tls.crt` and `tls.key` containing the TLS certificate and key.
258
+
This is the format produced by `kubectl create secret tls <secret_name> --cert=<cert_file> --key=<key_file>`.
259
+
260
+
1. Set `tlsCertSecretName` to the name of the secret, as shown below:
261
+
262
+
```yaml
263
+
# Helm chart values.yaml
264
+
265
+
replicated:
266
+
tlsCertSecretName: YOUR_TLS_SECRET
267
+
```
268
+
Where `YOUR_TLS_SECRET` is the secret in the namespace containing the TLS certificate and key.
0 commit comments