Skip to content

fix: use tls.crt/tls.key key names consistently in certbot guide #541

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
yesterdaysrebel merged 1 commit into from
Aug 6, 2026
Merged

fix: use tls.crt/tls.key key names consistently in certbot guide #541

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 4 additions & 4 deletions docs/deploy-applications/custom-domain-certificates/certbot-manual.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,8 +45,8 @@ Tips:
In your environment's OpenBao/Vault UI (see [Managing Environment Secrets](/deploy-applications/manage-environment-secrets)), create a secret at a dedicated path:

- Path: `secret/<your-app>-tls`
- Key `tls_crt`: contents of `fullchain.pem`
- Key `tls_key`: contents of `privkey.pem`
- Key `tls.crt`: contents of `fullchain.pem`
- Key `tls.key`: contents of `privkey.pem`

## Step 3 — Reference it from your application values

Expand All @@ -71,11 +71,11 @@ externalSecret:
"tls.crt":
remoteRef:
key: secret/<your-app>-tls
property: tls_crt
property: tls.crt
"tls.key":
remoteRef:
key: secret/<your-app>-tls
property: tls_key
property: tls.key

ingress:
enabled: true
Expand Down
Loading