Provisioning a CA and Generating TLS Certificates

In this lab you will provision a PKI Infrastructure using CloudFlare’s PKI toolkit, cfssl, then use it to bootstrap a Certificate Authority, and generate TLS certificates for the following components: etcd, kube-apiserver, kube-controller-manager, kube-scheduler, kubelet, and kube-proxy.

Certificate Authority

In this section you will provision a Certificate Authority that can be used to generate additional TLS certificates.

Generate the CA configuration file, certificate, and private key:

  1. {
  3. cat > ca-config.json <<EOF
  4. {
  5.   "signing": {
  6.     "default": {
  7.       "expiry": "8760h"
  8.     },
  9.     "profiles": {
  10.       "kubernetes": {
  11.         "usages": ["signing", "key encipherment", "server auth", "client auth"],
  12.         "expiry": "8760h"
  13.       }
  14.     }
  15.   }
  16. }
  17. EOF
  19. cat > ca-csr.json <<EOF
  20. {
  21.   "CN": "Kubernetes",
  22.   "key": {
  23.     "algo": "rsa",
  24.     "size": 2048
  25.   },
  26.   "names": [
  27.     {
  28.       "C": "US",
  29.       "L": "Portland",
  30.       "O": "Kubernetes",
  31.       "OU": "CA",
  32.       "ST": "Oregon"
  33.     }
  34.   ]
  35. }
  36. EOF
  38. cfssl gencert -initca ca-csr.json | cfssljson -bare ca
  40. }

Results:

  1. ca-key.pem
  2. ca.pem

Client and Server Certificates

In this section you will generate client and server certificates for each Kubernetes component and a client certificate for the Kubernetes admin user.

The Admin Client Certificate

Generate the admin client certificate and private key:

  1. {
  3. cat > admin-csr.json <<EOF
  4. {
  5.   "CN": "admin",
  6.   "key": {
  7.     "algo": "rsa",
  8.     "size": 2048
  9.   },
  10.   "names": [
  11.     {
  12.       "C": "US",
  13.       "L": "Portland",
  14.       "O": "system:masters",
  15.       "OU": "Kubernetes The Hard Way",
  16.       "ST": "Oregon"
  17.     }
  18.   ]
  19. }
  20. EOF
  22. cfssl gencert \
  23.   -ca=ca.pem \
  24.   -ca-key=ca-key.pem \
  25.   -config=ca-config.json \
  26.   -profile=kubernetes \
  27.   admin-csr.json | cfssljson -bare admin
  29. }

Results:

  1. admin-key.pem
  2. admin.pem

The Kubelet Client Certificates

Kubernetes uses a special-purpose authorization mode called Node Authorizer, that specifically authorizes API requests made by Kubelets. In order to be authorized by the Node Authorizer, Kubelets must use a credential that identifies them as being in the system:nodes group, with a username of system:node:<nodeName>. In this section you will create a certificate for each Kubernetes worker node that meets the Node Authorizer requirements.

Generate a certificate and private key for each Kubernetes worker node:

  1. for instance in worker-0 worker-1 worker-2; do
  2. cat > ${instance}-csr.json <<EOF
  3. {
  4.   "CN": "system:node:${instance}",
  5.   "key": {
  6.     "algo": "rsa",
  7.     "size": 2048
  8.   },
  9.   "names": [
  10.     {
  11.       "C": "US",
  12.       "L": "Portland",
  13.       "O": "system:nodes",
  14.       "OU": "Kubernetes The Hard Way",
  15.       "ST": "Oregon"
  16.     }
  17.   ]
  18. }
  19. EOF
  21. EXTERNAL_IP=$(gcloud compute instances describe ${instance} \
  22.   --format 'value(networkInterfaces[0].accessConfigs[0].natIP)')
  24. INTERNAL_IP=$(gcloud compute instances describe ${instance} \
  25.   --format 'value(networkInterfaces[0].networkIP)')
  27. cfssl gencert \
  28.   -ca=ca.pem \
  29.   -ca-key=ca-key.pem \
  30.   -config=ca-config.json \
  31.   -hostname=${instance},${EXTERNAL_IP},${INTERNAL_IP} \
  32.   -profile=kubernetes \
  33.   ${instance}-csr.json | cfssljson -bare ${instance}
  34. done

Results:

  1. worker-0-key.pem
  2. worker-0.pem
  3. worker-1-key.pem
  4. worker-1.pem
  5. worker-2-key.pem
  6. worker-2.pem

The Controller Manager Client Certificate

Generate the kube-controller-manager client certificate and private key:

  1. {
  3. cat > kube-controller-manager-csr.json <<EOF
  4. {
  5.   "CN": "system:kube-controller-manager",
  6.   "key": {
  7.     "algo": "rsa",
  8.     "size": 2048
  9.   },
  10.   "names": [
  11.     {
  12.       "C": "US",
  13.       "L": "Portland",
  14.       "O": "system:kube-controller-manager",
  15.       "OU": "Kubernetes The Hard Way",
  16.       "ST": "Oregon"
  17.     }
  18.   ]
  19. }
  20. EOF
  22. cfssl gencert \
  23.   -ca=ca.pem \
  24.   -ca-key=ca-key.pem \
  25.   -config=ca-config.json \
  26.   -profile=kubernetes \
  27.   kube-controller-manager-csr.json | cfssljson -bare kube-controller-manager
  29. }

Results:

  1. kube-controller-manager-key.pem
  2. kube-controller-manager.pem

The Kube Proxy Client Certificate

Generate the kube-proxy client certificate and private key:

  1. {
  3. cat > kube-proxy-csr.json <<EOF
  4. {
  5.   "CN": "system:kube-proxy",
  6.   "key": {
  7.     "algo": "rsa",
  8.     "size": 2048
  9.   },
  10.   "names": [
  11.     {
  12.       "C": "US",
  13.       "L": "Portland",
  14.       "O": "system:node-proxier",
  15.       "OU": "Kubernetes The Hard Way",
  16.       "ST": "Oregon"
  17.     }
  18.   ]
  19. }
  20. EOF
  22. cfssl gencert \
  23.   -ca=ca.pem \
  24.   -ca-key=ca-key.pem \
  25.   -config=ca-config.json \
  26.   -profile=kubernetes \
  27.   kube-proxy-csr.json | cfssljson -bare kube-proxy
  29. }

Results:

  1. kube-proxy-key.pem
  2. kube-proxy.pem

The Scheduler Client Certificate

Generate the kube-scheduler client certificate and private key:

  1. {
  3. cat > kube-scheduler-csr.json <<EOF
  4. {
  5.   "CN": "system:kube-scheduler",
  6.   "key": {
  7.     "algo": "rsa",
  8.     "size": 2048
  9.   },
  10.   "names": [
  11.     {
  12.       "C": "US",
  13.       "L": "Portland",
  14.       "O": "system:kube-scheduler",
  15.       "OU": "Kubernetes The Hard Way",
  16.       "ST": "Oregon"
  17.     }
  18.   ]
  19. }
  20. EOF
  22. cfssl gencert \
  23.   -ca=ca.pem \
  24.   -ca-key=ca-key.pem \
  25.   -config=ca-config.json \
  26.   -profile=kubernetes \
  27.   kube-scheduler-csr.json | cfssljson -bare kube-scheduler
  29. }

Results:

  1. kube-scheduler-key.pem
  2. kube-scheduler.pem

The Kubernetes API Server Certificate

The kubernetes-the-hard-way static IP address will be included in the list of subject alternative names for the Kubernetes API Server certificate. This will ensure the certificate can be validated by remote clients.

Generate the Kubernetes API Server certificate and private key:

  1. {
  3. KUBERNETES_PUBLIC_ADDRESS=$(gcloud compute addresses describe kubernetes-the-hard-way \
  4.   --region $(gcloud config get-value compute/region) \
  5.   --format 'value(address)')
  7. KUBERNETES_HOSTNAMES=kubernetes,kubernetes.default,kubernetes.default.svc,kubernetes.default.svc.cluster,kubernetes.svc.cluster.local
  9. cat > kubernetes-csr.json <<EOF
  10. {
  11.   "CN": "kubernetes",
  12.   "key": {
  13.     "algo": "rsa",
  14.     "size": 2048
  15.   },
  16.   "names": [
  17.     {
  18.       "C": "US",
  19.       "L": "Portland",
  20.       "O": "Kubernetes",
  21.       "OU": "Kubernetes The Hard Way",
  22.       "ST": "Oregon"
  23.     }
  24.   ]
  25. }
  26. EOF
  28. cfssl gencert \
  29.   -ca=ca.pem \
  30.   -ca-key=ca-key.pem \
  31.   -config=ca-config.json \
  32.   -hostname=10.32.0.1,10.240.0.10,10.240.0.11,10.240.0.12,${KUBERNETES_PUBLIC_ADDRESS},127.0.0.1,${KUBERNETES_HOSTNAMES} \
  33.   -profile=kubernetes \
  34.   kubernetes-csr.json | cfssljson -bare kubernetes
  36. }

The Kubernetes API server is automatically assigned the kubernetes internal dns name, which will be linked to the first IP address (10.32.0.1) from the address range (10.32.0.0/24) reserved for internal cluster services during the control plane bootstrapping lab.

Results:

  1. kubernetes-key.pem
  2. kubernetes.pem

The Service Account Key Pair

The Kubernetes Controller Manager leverages a key pair to generate and sign service account tokens as described in the managing service accounts documentation.

Generate the service-account certificate and private key:

  1. {
  3. cat > service-account-csr.json <<EOF
  4. {
  5.   "CN": "service-accounts",
  6.   "key": {
  7.     "algo": "rsa",
  8.     "size": 2048
  9.   },
  10.   "names": [
  11.     {
  12.       "C": "US",
  13.       "L": "Portland",
  14.       "O": "Kubernetes",
  15.       "OU": "Kubernetes The Hard Way",
  16.       "ST": "Oregon"
  17.     }
  18.   ]
  19. }
  20. EOF
  22. cfssl gencert \
  23.   -ca=ca.pem \
  24.   -ca-key=ca-key.pem \
  25.   -config=ca-config.json \
  26.   -profile=kubernetes \
  27.   service-account-csr.json | cfssljson -bare service-account
  29. }

Results:

  1. service-account-key.pem
  2. service-account.pem

Distribute the Client and Server Certificates

Copy the appropriate certificates and private keys to each worker instance:

  1. for instance in worker-0 worker-1 worker-2; do
  2.   gcloud compute scp ca.pem ${instance}-key.pem ${instance}.pem ${instance}:~/
  3. done

Copy the appropriate certificates and private keys to each controller instance:

  1. for instance in controller-0 controller-1 controller-2; do
  2.   gcloud compute scp ca.pem ca-key.pem kubernetes-key.pem kubernetes.pem \
  3.     service-account-key.pem service-account.pem ${instance}:~/
  4. done

The kube-proxy, kube-controller-manager, kube-scheduler, and kubelet client certificates will be used to generate client authentication configuration files in the next lab.

Next: Generating Kubernetes Configuration Files for Authentication