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**
CAca.crt, ca.keyKUBERNETES-CASelf
Adminadmin.crtkube-adminCA
API Serverapiserver.crtkube-apiserverCA
etcdetcdserver.crtetcd-serverCA
Kubeletnode01.crtsystem\:node\:node01CA
## πŸ› οΈ Production Setup (kubeadm) > πŸ’‘ **πŸ’‘ Tip: **Production မှာ manually α€™α€œα€―α€•α€Ία€›! kubeadm α€€ auto generate α€œα€―α€•α€Ία€•α€±α€Έα€α€šα€Ία‹ ```bash # Certificate location ls /etc/kubernetes/pki/

Check expiry

kubeadm certs check-expiration

Renew certificates

kubeadm certs renew all