ahmza.com/k8s-starter-pack
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Switch demo.ahmza.com to production Let's Encrypt certificate

Browse Source
This commit is contained in:
ahmza
2026-09-03 05:19:44 +01:00
parent a5f4041d47
commit e88819f222
1 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
apps/demo/ingress.yaml
+5 -4
View File
@@ -10,16 +10,17 @@
# cert-manager.io/cluster-issuer triggers cert-manager's "ingress-shim": it # cert-manager.io/cluster-issuer triggers cert-manager's "ingress-shim": it
# notices this annotation, creates a Certificate resource for the # notices this annotation, creates a Certificate resource for the
# hostname(s) in tls.hosts below, and keeps it renewed automatically # hostname(s) in tls.hosts below, and keeps it renewed automatically
# forever. Deliberately pointed at letsencrypt-staging first — see # forever. This was proven against letsencrypt-staging first — see
# docs/12-cert-manager.md for why, and switch to letsencrypt-prod only # docs/12-cert-manager.md — before switching to the real, browser-trusted
# after confirming staging actually works for this hostname. # letsencrypt-prod here. Always prove a new hostname against staging
# first; production has much stricter rate limits.
apiVersion: networking.k8s.io/v1 apiVersion: networking.k8s.io/v1
kind: Ingress kind: Ingress
metadata: metadata:
name: demo name: demo
namespace: demo namespace: demo
annotations: annotations:
cert-manager.io/cluster-issuer: letsencrypt-staging cert-manager.io/cluster-issuer: letsencrypt-prod
spec: spec:
tls: tls:
- hosts: - hosts: