TLS Certificates - Step by Step Guide
September 15, 2026
Β π Overview
TLS (Transport Layer Security) α Kubernetes cluster αα²α components αα½α± α‘αα»ααΊαΈαα»ααΊαΈ secure communication αα―ααΊααα―α· α‘αα―αΆαΈααΌα―αααΊα
βΉοΈ αα¬ααΌα±α¬αα·αΊ ααα―αα²:
π Encryption - Data ααα― encrypt αα―ααΊαααΊ
β Authentication - Identity verify αα―ααΊαααΊ
π‘οΈ Integrity - Data tampering αα¬αα½ααΊαααΊ
ποΈ Certificate Architecture
Certificate Hierarchy:
ββββββββββββββββββββββββββββββββββββ
β CA (Certificate Authority) β
β - Root of Trust β
β - Signs all certificates β
β - Files: ca.crt, ca.key β
ββββββββββββ¬ββββββββββββββββββββββββ
β
ββββββββ΄βββββββ¬βββββββββββββββ
β β β
βββββΌβββββ ββββββΌβββββ βββββββΌββββββ
β Client β β Server β β System β
β Certs β β Certs β β Certs β
ββββββββββ βββββββββββ βββββββββββββ
π§ Certificate Types
π 1. CA Certificate (Root)
β’ Purpose: Sign all other certificates
β’ Files: ca.crt, ca.key
β’ β οΈ Critical: Private key ααα― secure αα¬αΈααααΊ! π€ 2. Client Certificates
β’ Admin: kube-admin (system:masters group)
β’ Scheduler: system:kube-scheduler
β’ Controller: system:kube-controller-manager
β’ Proxy: system:kube-proxy π₯οΈ 3. Server Certificates
β’ API Server: apiserver.crt (+ SANs)
β’ etcd: etcdserver.crt
β’ Kubelet: node-specific certificates
π Step-by-Step Guide
Step 1: Create CA Certificate
**
π― Goal: **Root certificate authority αααΊαα±α¬ααΊαα¬
# 1. Generate CA private key (2048-bit RSA)
openssl genrsa -out ca.key 2048
# 2. Create Certificate Signing Request (CSR)
openssl req -new -key ca.key -subj "/CN=KUBERNETES-CA" -out ca.csr
# 3. Self-sign the CA certificate
openssl x509 -req -in ca.csr -signkey ca.key -out ca.crt
π¦ Output Files:
β ca.key - CA private key (π Keep secret!)
β ca.crt - CA public certificate (share to cluster)
Step 2: Admin User Certificate
**
π€ Goal: **Admin user authentication α‘αα½ααΊ certificate
Basic Method:
# 1. Generate admin private key
openssl genrsa -out admin.key 2048
# 2. Create admin CSR
openssl req -new -key admin.key -subj "/CN=kube-admin" -out admin.csr
# 3. Sign with CA
openssl x509 -req -in admin.csr -CA ca.crt -CAkey ca.key -out admin.crt
With Admin Privileges (Recommended):
# Include organization for system:masters group
openssl req -new -key admin.key \
-subj "/CN=kube-admin/O=system:masters" \
-out admin.csr
openssl x509 -req -in admin.csr -CA ca.crt -CAkey ca.key -out admin.crt
π‘ Key Points:
β’ CN=kube-admin - Username
β’ O=system:masters - Admin group membership
β’ CA α sign αα―ααΊαα±αΈαααΊ (trusted certificate)
Step 3: System Component Certificates
# Template for system components
COMPONENT="kube-scheduler" # or kube-controller-manager, kube-proxy
openssl genrsa -out ${COMPONENT}.key 2048
openssl req -new -key ${COMPONENT}.key \
-subj "/CN=system:${COMPONENT}" \
-out ${COMPONENT}.csr
openssl x509 -req -in ${COMPONENT}.csr \
-CA ca.crt -CAkey ca.key \
-out ${COMPONENT}.crt
π Naming Convention:
β Always prefix with system:
β Examples: system:kube-scheduler, system:kube-proxy
Step 4: API Server Certificate (Complex)
**
π Goal: **API server certificate with multiple SANs (Subject Alternative Names)
β οΈ **β οΈ Challenge: **API server α multiple names/IPs αα²α· access αα―ααΊααα―α·ααααΊ
Alternate Names:
β’ DNS: kubernetes, kubernetes.default, kubernetes.default.svc
β’ IPs: 10.96.0.1 (ClusterIP), 172.17.0.87 (Node IP)
π Using Certificates
Method 1: Direct curl Command
curl https://kube-apiserver:6443/api/v1/pods \
--key admin.key \
--cert admin.crt \
--cacert ca.crt
Method 2: kubeconfig File
apiVersion: v1
clusters:
- cluster:
certificate-authority: /path/to/ca.crt
server: https://kube-apiserver:6443
name: kubernetes
kind: Config
users:
- name: kubernetes-admin
user:
client-certificate: /path/to/admin.crt
client-key: /path/to/admin.key
π Certificate Verification
# Decode certificate
openssl x509 -in admin.crt -text -noout
# Check expiry
openssl x509 -in apiserver.crt -noout -dates
# kubeadm check (production)
kubeadm certs check-expiration
π Security Best Practices
π 1. Protect Private Keys
β Never commit to Git
β chmod 600 *.key
β Store in secrets management (Vault, AWS Secrets Manager) π 2. Certificate Rotation
π Default validity: 1 year
π Auto-renewal with kubeadm
β° Set reminders 30 days before expiry π¨ 3. CA Certificate
π Most critical certificate
πΎ Backup securely
π¨ If compromised β entire cluster compromised
β Summary
Certificate Flow:
1. Create CA
2. Generate client certs (admin, scheduler, etc.)
3. Generate server certs (API server, etcd, kubelet)
4. Configure components with cert paths
5. Monitor & renew before expiry π π Key Takeaways:
1οΈβ£ CA Certificate - Root of trust, signs all certificates
2οΈβ£ Client Certificates - Authentication purposes
3οΈβ£ Server Certificates - Encryption + authentication
4οΈβ£ Production - Use kubeadm (auto-generated)
5οΈβ£ Monitor expiry dates & implement rotation strategy
π Complete Certificate List
| **Component** | **Certificate** | **Common Name** | **Signed By** |
| CA | ca.crt, ca.key | KUBERNETES-CA | Self |
| Admin | admin.crt | kube-admin | CA |
| API Server | apiserver.crt | kube-apiserver | CA |
| etcd | etcdserver.crt | etcd-server | CA |
| Kubelet | node01.crt | system\:node\:node01 | CA |
Check expiry
kubeadm certs check-expiration
Renew certificates
kubeadm certs renew all