Auto-update blog content from Obsidian: 2025-08-18 15:19:50
All checks were successful
Blog Deployment / Check-Rebuild (push) Successful in 7s
Blog Deployment / Build (push) Has been skipped
Blog Deployment / Deploy-Staging (push) Successful in 12s
Blog Deployment / Test-Staging (push) Successful in 3s
Blog Deployment / Merge (push) Successful in 8s
Blog Deployment / Deploy-Production (push) Successful in 24s
Blog Deployment / Test-Production (push) Successful in 10s
Blog Deployment / Clean (push) Has been skipped
Blog Deployment / Notify (push) Successful in 10s

This commit is contained in:
Gitea Actions
2025-08-18 15:19:50 +00:00
parent a160e45ff3
commit 650808a9c0

View File

@@ -465,13 +465,24 @@ Test Ingress on HTTP
---
## Secure Connection with TLS
oneline to explain how to use https
Exposing services over HTTP works, but in practice we almost always want to use **HTTPS**. Thats where TLS certificates comes in, it encrypts traffic between clients and your cluster, ensuring security and trust.
### Cert-Manager
To automate certificate management in Kubernetes, we use **Cert-Manager**. It can request, renew, and manage TLS certificates without manual intervention.
#### Install Cert-Manager
install with helm
We deploy it with Helm on the cluster:
```bash
helm repo add jetstack https://charts.jetstack.io
helm repo update
helm install cert-manager jetstack/cert-manager \
--namespace cert-manager \
--create-namespace \
--set crds.enabled=true
```
#### Setup Cert-Manager
verify clusterissuer