Skip to content

document 'tlsCertSecretName' param #3309

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jun 13, 2025
Merged

document 'tlsCertSecretName' param #3309

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
3b84516
document 'tlsCertSecretName' param
laverya Jun 13, 2025
5589195
move to customizing
laverya Jun 13, 2025
8304082
Update replicated-sdk-customizing.md
paigecalvert Jun 13, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 20 additions & 1 deletion docs/vendor/replicated-sdk-customizing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -246,4 +246,23 @@ replicated:
podLabels:
monitoring: enabled
custom.company.io/pod-label: value
```
```

## Enable SSL

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.

To configure the Replicated SDK pod to serve traffic over SSL:

1. Ensure a secret exists in the namespace with keys `tls.crt` and `tls.key` containing the TLS certificate and key.
This is the format produced by `kubectl create secret tls <secret_name> --cert=<cert_file> --key=<key_file>`.

1. Set `tlsCertSecretName` to the name of the secret, as shown below:

```yaml
# Helm chart values.yaml

replicated:
tlsCertSecretName: YOUR_TLS_SECRET
```
Where `YOUR_TLS_SECRET` is the secret in the namespace containing the TLS certificate and key.