Skip to content

Commit 9f6f62a

Browse files
authored
Merge pull request #3309 from replicatedhq/laverya/sc-124935/document-tls-for-sdk
document 'tlsCertSecretName' param
2 parents 44e1841 + 8304082 commit 9f6f62a

File tree

1 file changed

+20
-1
lines changed

1 file changed

+20
-1
lines changed

docs/vendor/replicated-sdk-customizing.md

Lines changed: 20 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -246,4 +246,23 @@ replicated:
246246
podLabels:
247247
monitoring: enabled
248248
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

Comments
 (0)