diff --git a/README.md b/README.md index 58dfdab..9627793 100644 --- a/README.md +++ b/README.md @@ -1,11 +1,5 @@ > This tutorial is a modified version of the original developed by [Kelsey Hightower](https://github.com/kelseyhightower/kubernetes-the-hard-way). -This repository holds the supporting material for the [Certified Kubernetes Administrators Course](https://kodekloud.com/p/certified-kubernetes-administrator-with-practice-tests). There are two major sections. - -- [Kubernetes The Hard Way on VirtualBox](#kubernetes-the-hard-way-on-virtualbox) -- [Answers to Practice Tests hosted on KodeKloud](/practice-questions-answers) - - # Kubernetes The Hard Way On VirtualBox This tutorial walks you through setting up Kubernetes the hard way on a local machine using VirtualBox. diff --git a/deployments/coredns.yaml b/deployments/coredns.yaml index 352dcd4..23cdafd 100644 --- a/deployments/coredns.yaml +++ b/deployments/coredns.yaml @@ -62,7 +62,7 @@ data: loadbalance } --- -apiVersion: extensions/v1beta1 +apiVersion: apps/v1 kind: Deployment metadata: name: coredns diff --git a/docs/01-prerequisites.md b/docs/01-prerequisites.md index 4e79b7e..824b791 100644 --- a/docs/01-prerequisites.md +++ b/docs/01-prerequisites.md @@ -2,7 +2,7 @@ ## VM Hardware Requirements -8 GB of RAM (Preferebly 16 GB) +8 GB of RAM (Preferably 16 GB) 50 GB Disk space ## Virtual Box @@ -26,4 +26,4 @@ Download and Install [Vagrant](https://www.vagrantup.com/) on your platform. - Centos - Linux - macOS -- Arch Linux \ No newline at end of file +- Arch Linux diff --git a/docs/02-compute-resources.md b/docs/02-compute-resources.md index a06c070..852e03d 100644 --- a/docs/02-compute-resources.md +++ b/docs/02-compute-resources.md @@ -73,7 +73,7 @@ Vagrant generates a private key for each of these VMs. It is placed under the .v ## Troubleshooting Tips -If any of the VMs failed to provision, or is not configured correct, delete the vm using the command: +1. If any of the VMs failed to provision, or is not configured correct, delete the vm using the command: `vagrant destroy ` @@ -97,3 +97,11 @@ In such cases delete the VM, then delete the VM folder and then re-provision `rmdir "\kubernetes-ha-worker-2"` `vagrant up` + +2. When you try "sysctl net.bridge.bridge-nf-call-iptables=1", it would sometimes return "sysctl: cannot stat /proc/sys/net/bridge/bridge-nf-call-iptables: No such file or directory" error. The below would resolve the issue. + +`modprobe br_netfilter` + +`sysctl -p /etc/sysctl.conf` + +`net.bridge.bridge-nf-call-iptables=1` diff --git a/docs/05-kubernetes-configuration-files.md b/docs/05-kubernetes-configuration-files.md index 7dec4ff..4d945d8 100644 --- a/docs/05-kubernetes-configuration-files.md +++ b/docs/05-kubernetes-configuration-files.md @@ -45,10 +45,9 @@ Results: ``` kube-proxy.kubeconfig - +``` Reference docs for kube-proxy [here](https://kubernetes.io/docs/reference/command-line-tools-reference/kube-proxy/) -``` ### The kube-controller-manager Kubernetes Configuration File diff --git a/docs/06-data-encryption-keys.md b/docs/06-data-encryption-keys.md index 4d6392c..f1f155a 100644 --- a/docs/06-data-encryption-keys.md +++ b/docs/06-data-encryption-keys.md @@ -39,6 +39,15 @@ for instance in master-1 master-2; do scp encryption-config.yaml ${instance}:~/ done ``` + +Move `encryption-config.yaml` encryption config file to appropriate directory. + +``` +for instance in master-1 master-2; do + ssh ${instance} sudo mv encryption-config.yaml /var/lib/kubernetes/ +done +``` + Reference: https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/#encrypting-your-data Next: [Bootstrapping the etcd Cluster](07-bootstrapping-etcd.md) diff --git a/docs/07-bootstrapping-etcd.md b/docs/07-bootstrapping-etcd.md index 2a01a4c..0fa2027 100644 --- a/docs/07-bootstrapping-etcd.md +++ b/docs/07-bootstrapping-etcd.md @@ -8,7 +8,7 @@ The commands in this lab must be run on each controller instance: `master-1`, an ### Running commands in parallel with tmux -[tmux](https://github.com/tmux/tmux/wiki) can be used to run commands on multiple compute instances at the same time. See the [Running commands in parallel with tmux](01-prerequisites.md#running-commands-in-parallel-with-tmux) section in the Prerequisites lab. +[tmux](https://github.com/tmux/tmux/wiki) can be used to run commands on multiple compute instances at the same time. ## Bootstrapping an etcd Cluster Member diff --git a/docs/08-bootstrapping-kubernetes-controllers.md b/docs/08-bootstrapping-kubernetes-controllers.md index 761aba8..8b3d358 100644 --- a/docs/08-bootstrapping-kubernetes-controllers.md +++ b/docs/08-bootstrapping-kubernetes-controllers.md @@ -78,7 +78,7 @@ Documentation=https://github.com/kubernetes/kubernetes ExecStart=/usr/local/bin/kube-apiserver \\ --advertise-address=${INTERNAL_IP} \\ --allow-privileged=true \\ - --apiserver-count=3 \\ + --apiserver-count=2 \\ --audit-log-maxage=30 \\ --audit-log-maxbackup=3 \\ --audit-log-maxsize=100 \\ @@ -99,7 +99,7 @@ ExecStart=/usr/local/bin/kube-apiserver \\ --kubelet-client-certificate=/var/lib/kubernetes/kube-apiserver.crt \\ --kubelet-client-key=/var/lib/kubernetes/kube-apiserver.key \\ --kubelet-https=true \\ - --runtime-config=api/all \\ + --runtime-config=api/all=true \\ --service-account-key-file=/var/lib/kubernetes/service-account.crt \\ --service-cluster-ip-range=10.96.0.0/24 \\ --service-node-port-range=30000-32767 \\ diff --git a/docs/10-tls-bootstrapping-kubernetes-workers.md b/docs/10-tls-bootstrapping-kubernetes-workers.md index f7aa8c4..48d1ec6 100644 --- a/docs/10-tls-bootstrapping-kubernetes-workers.md +++ b/docs/10-tls-bootstrapping-kubernetes-workers.md @@ -14,7 +14,11 @@ This is not a practical approach when you have 1000s of nodes in the cluster, an - The Nodes can retrieve the signed certificate from the Kubernetes CA - The Nodes can generate a kube-config file using this certificate by themselves - The Nodes can start and join the cluster by themselves -- The Nodes can renew certificates when they expire by themselves +- The Nodes can request new certificates via a CSR, but the CSR must be manually approved by a cluster administrator + +In Kubernetes 1.11 a patch was merged to require administrator or Controller approval of node serving CSRs for security reasons. + +Reference: https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet-tls-bootstrapping/#certificate-rotation So let's get started! @@ -39,16 +43,13 @@ So let's get started! Copy the ca certificate to the worker node: -``` -scp /var/lib/kubernetes/ca.crt worker-2:~/ -``` ## Step 1 Configure the Binaries on the Worker node ### Download and Install Worker Binaries ``` -wget -q --show-progress --https-only --timestamping \ +worker-2$ wget -q --show-progress --https-only --timestamping \ https://storage.googleapis.com/kubernetes-release/release/v1.13.0/bin/linux/amd64/kubectl \ https://storage.googleapis.com/kubernetes-release/release/v1.13.0/bin/linux/amd64/kube-proxy \ https://storage.googleapis.com/kubernetes-release/release/v1.13.0/bin/linux/amd64/kubelet @@ -59,7 +60,7 @@ Reference: https://kubernetes.io/docs/setup/release/#node-binaries Create the installation directories: ``` -sudo mkdir -p \ +worker-2$ sudo mkdir -p \ /etc/cni/net.d \ /opt/cni/bin \ /var/lib/kubelet \ @@ -78,7 +79,7 @@ Install the worker binaries: ``` ### Move the ca certificate -`sudo mv ca.crt /var/lib/kubernetes/` +`worker-2$ sudo mv ca.crt /var/lib/kubernetes/` # Step 1 Create the Boostrap Token to be used by Nodes(Kubelets) to invoke Certificate API @@ -86,10 +87,10 @@ For the workers(kubelet) to access the Certificates API, they need to authentica Bootstrap Tokens take the form of a 6 character token id followed by 16 character token secret separated by a dot. Eg: abcdef.0123456789abcdef. More formally, they must match the regular expression [a-z0-9]{6}\.[a-z0-9]{16} -Bootstrap Tokens are created as a secret in the kube-system namespace. + ``` -cat > bootstrap-token-07401b.yaml < bootstrap-token-07401b.yaml < csrs-for-bootstrapping.yaml < csrs-for-bootstrapping.yaml < auto-approve-csrs-for-group.yaml < auto-approve-csrs-for-group.yaml < auto-approve-renewals-for-nodes.yaml < auto-approve-renewals-for-nodes.yaml < Note: This may take a few minutes depending on your network speed -## Extract the Version +## Use the version specific to your cluster ``` -kubetest --extract=v1.13.0 +K8S_VERSION=$(kubectl version -o json | jq -r '.serverVersion.gitVersion') +export KUBERNETES_CONFORMANCE_TEST=y +export KUBECONFIG="$HOME/.kube/config" -cd kubernetes -export KUBE_MASTER_IP="192.168.5.11:6443" -export KUBE_MASTER=master-1 - -kubetest --test --provider=skeleton --test_args="--ginkgo.focus=\[Conformance\]" | tee test.out +kubetest --provider=skeleton --test --test_args=”--ginkgo.focus=\[Conformance\]” --extract ${K8S_VERSION} | tee test.out ``` diff --git a/docs/17-extra-dynamic-kubelet-configuration.md b/docs/17-extra-dynamic-kubelet-configuration.md index 9ad9856..bccc52d 100644 --- a/docs/17-extra-dynamic-kubelet-configuration.md +++ b/docs/17-extra-dynamic-kubelet-configuration.md @@ -11,9 +11,18 @@ NODE_NAME="worker-1"; NODE_NAME="worker-1"; curl -sSL "https://localhost:6443/ap kubectl -n kube-system create configmap nodes-config --from-file=kubelet=kubelet_configz_${NODE_NAME} --append-hash -o yaml ``` -Edit node to use the dynamically created configuration +Edit `worker-1` node to use the dynamically created configuration ``` -kubectl edit worker-2 +master-1# kubectl edit node worker-1 +``` + +Add the following YAML bit under `spec`: +``` +configSource: + configMap: + name: CONFIG_MAP_NAME # replace CONFIG_MAP_NAME with the name of the ConfigMap + namespace: kube-system + kubeletConfigKey: kubelet ``` Configure Kubelet Service @@ -45,3 +54,5 @@ RestartSec=5 WantedBy=multi-user.target EOF ``` + +Reference: https://kubernetes.io/docs/tasks/administer-cluster/reconfigure-kubelet/ diff --git a/practice-questions-answers/cluster-maintenance/backup-etcd/etcd-backup-and-restore.md b/practice-questions-answers/cluster-maintenance/backup-etcd/etcd-backup-and-restore.md index 84234fb..ad05cf8 100644 --- a/practice-questions-answers/cluster-maintenance/backup-etcd/etcd-backup-and-restore.md +++ b/practice-questions-answers/cluster-maintenance/backup-etcd/etcd-backup-and-restore.md @@ -5,7 +5,7 @@ Reference: https://github.com/etcd-io/etcd/releases ``` -ETCD_VER=v3.3.13 +ETCD_VER=v3.4.9 # choose either URL GOOGLE_URL=https://storage.googleapis.com/etcd @@ -30,9 +30,15 @@ mv /tmp/etcd-download-test/etcdctl /usr/bin ``` ETCDCTL_API=3 etcdctl --endpoints=https://[127.0.0.1]:2379 --cacert=/etc/kubernetes/pki/etcd/ca.crt \ --cert=/etc/kubernetes/pki/etcd/server.crt --key=/etc/kubernetes/pki/etcd/server.key \ - snapshot save /tmp/snapshot-pre-boot.db + snapshot save /opt/snapshot-pre-boot.db ``` +Note: In this case, the **ETCD** is running on the same server where we are running the commands (which is the *controlplane* node). As a result, the **--endpoint** argument is optional and can be ignored. + +The options **--cert, --cacert and --key** are mandatory to authenticate to the ETCD server to take the backup. + +If you want to take a backup of the ETCD service running on a different machine, you will have to provide the correct endpoint to that server (which is the IP Address and port of the etcd server with the **--endpoint** argument) + # ----------------------------- # Disaster Happens # ----------------------------- @@ -40,51 +46,34 @@ ETCDCTL_API=3 etcdctl --endpoints=https://[127.0.0.1]:2379 --cacert=/etc/kuberne # 3. Restore ETCD Snapshot to a new folder ``` -ETCDCTL_API=3 etcdctl --endpoints=https://[127.0.0.1]:2379 --cacert=/etc/kubernetes/pki/etcd/ca.crt \ - --name=master \ - --cert=/etc/kubernetes/pki/etcd/server.crt --key=/etc/kubernetes/pki/etcd/server.key \ - --data-dir /var/lib/etcd-from-backup \ - --initial-cluster=master=https://127.0.0.1:2380 \ - --initial-cluster-token etcd-cluster-1 \ - --initial-advertise-peer-urls=https://127.0.0.1:2380 \ - snapshot restore /tmp/snapshot-pre-boot.db +ETCDCTL_API=3 etcdctl --data-dir /var/lib/etcd-from-backup \ + snapshot restore /opt/snapshot-pre-boot.db ``` +Note: In this case, we are restoring the snapshot to a different directory but in the same server where we took the backup (**the controlplane node)** +As a result, the only required option for the restore command is the **--data-dir**. + # 4. Modify /etc/kubernetes/manifests/etcd.yaml -Update ETCD POD to use the new data directory and cluster token by modifying the pod definition file at `/etc/kubernetes/manifests/etcd.yaml`. When this file is updated, the ETCD pod is automatically re-created as this is a static pod placed under the `/etc/kubernetes/manifests` directory. - -Update --data-dir to use new target location +We have now restored the etcd snapshot to a new path on the controlplane - **/var/lib/etcd-from-backup**, so, the only change to be made in the YAML file, is to change the hostPath for the volume called **etcd-data** from old directory (/var/lib/etcd) to the new directory **/var/lib/etcd-from-backup**. ``` ---data-dir=/var/lib/etcd-from-backup -``` - -Update new initial-cluster-token to specify new cluster - -``` ---initial-cluster-token=etcd-cluster-1 -``` - -Update volumes and volume mounts to point to new path - -``` - volumeMounts: - - mountPath: /var/lib/etcd-from-backup - name: etcd-data - - mountPath: /etc/kubernetes/pki/etcd - name: etcd-certs - hostNetwork: true - priorityClassName: system-cluster-critical volumes: - hostPath: path: /var/lib/etcd-from-backup type: DirectoryOrCreate name: etcd-data - - hostPath: - path: /etc/kubernetes/pki/etcd - type: DirectoryOrCreate - name: etcd-certs ``` +With this change, /var/lib/etcd on the **container** points to /var/lib/etcd-from-backup on the **controlplane** (which is what we want) -> Note: You don't really need to update data directory and volumeMounts.mountPath path above. You could simply just update the hostPath.path in the volumes section to point to the new directory. But if you are not working with a kubeadm deployed cluster, then you might have to update the data directory. That's why I left it as is. + +When this file is updated, the ETCD pod is automatically re-created as this is a static pod placed under the `/etc/kubernetes/manifests` directory. + + +> Note: as the ETCD pod has changed it will automatically restart, and also kube-controller-manager and kube-scheduler. Wait 1-2 to mins for this pods to restart. You can make a `watch "docker ps | grep etcd"` to see when the ETCD pod is restarted. + +> Note2: If the etcd pod is not getting `Ready 1/1`, then restart it by `kubectl delete pod -n kube-system etcd-controlplane` and wait 1 minute. + +> Note3: This is the simplest way to make sure that ETCD uses the restored data after the ETCD pod is recreated. You **don't** have to change anything else. + + **If** you do change **--data-dir** to **/var/lib/etcd-from-backup** in the YAML file, make sure that the **volumeMounts** for **etcd-data** is updated as well, with the mountPath pointing to /var/lib/etcd-from-backup (**THIS COMPLETE STEP IS OPTIONAL AND NEED NOT BE DONE FOR COMPLETING THE RESTORE**) diff --git a/tools/kubernetes-certs-checker.xlsx b/tools/kubernetes-certs-checker.xlsx index f385c66..009ecd6 100644 Binary files a/tools/kubernetes-certs-checker.xlsx and b/tools/kubernetes-certs-checker.xlsx differ diff --git a/vagrant/ubuntu/cert_verify.sh b/vagrant/ubuntu/cert_verify.sh index 705a53f..dc104e0 100755 --- a/vagrant/ubuntu/cert_verify.sh +++ b/vagrant/ubuntu/cert_verify.sh @@ -310,8 +310,8 @@ check_cert_kpkubeconfig() elif [ -f $KPKUBECONFIG ] then printf "${NC}kube-proxy kubeconfig file found, verifying the authenticity\n" - KPKUBECONFIG_SUBJECT=$(cat $KPKUBECONFIG | grep "client-certificate-data:" | awk '{print $2}' | base64 --decode | openssl x509 --text | grep "Subject: CN" | tr -d " ") - KPKUBECONFIG_ISSUER=$(cat $KPKUBECONFIG | grep "client-certificate-data:" | awk '{print $2}' | base64 --decode | openssl x509 --text | grep "Issuer: CN" | tr -d " ") + KPKUBECONFIG_SUBJECT=$(cat $KPKUBECONFIG | grep "client-certificate-data:" | awk '{print $2}' | base64 --decode | openssl x509 -text | grep "Subject: CN" | tr -d " ") + KPKUBECONFIG_ISSUER=$(cat $KPKUBECONFIG | grep "client-certificate-data:" | awk '{print $2}' | base64 --decode | openssl x509 -text | grep "Issuer: CN" | tr -d " ") KPKUBECONFIG_CERT_MD5=$(cat $KPKUBECONFIG | grep "client-certificate-data:" | awk '{print $2}' | base64 --decode | openssl x509 -noout | openssl md5 | awk '{print $2}') KPKUBECONFIG_KEY_MD5=$(cat $KPKUBECONFIG | grep "client-key-data" | awk '{print $2}' | base64 --decode | openssl rsa -noout | openssl md5 | awk '{print $2}') KPKUBECONFIG_SERVER=$(cat $KPKUBECONFIG | grep "server:"| awk '{print $2}') @@ -337,8 +337,8 @@ check_cert_kcmkubeconfig() elif [ -f $KCMKUBECONFIG ] then printf "${NC}kube-controller-manager kubeconfig file found, verifying the authenticity\n" - KCMKUBECONFIG_SUBJECT=$(cat $KCMKUBECONFIG | grep "client-certificate-data:" | awk '{print $2}' | base64 --decode | openssl x509 --text | grep "Subject: CN" | tr -d " ") - KCMKUBECONFIG_ISSUER=$(cat $KCMKUBECONFIG | grep "client-certificate-data:" | awk '{print $2}' | base64 --decode | openssl x509 --text | grep "Issuer: CN" | tr -d " ") + KCMKUBECONFIG_SUBJECT=$(cat $KCMKUBECONFIG | grep "client-certificate-data:" | awk '{print $2}' | base64 --decode | openssl x509 -text | grep "Subject: CN" | tr -d " ") + KCMKUBECONFIG_ISSUER=$(cat $KCMKUBECONFIG | grep "client-certificate-data:" | awk '{print $2}' | base64 --decode | openssl x509 -text | grep "Issuer: CN" | tr -d " ") KCMKUBECONFIG_CERT_MD5=$(cat $KCMKUBECONFIG | grep "client-certificate-data:" | awk '{print $2}' | base64 --decode | openssl x509 -noout | openssl md5 | awk '{print $2}') KCMKUBECONFIG_KEY_MD5=$(cat $KCMKUBECONFIG | grep "client-key-data" | awk '{print $2}' | base64 --decode | openssl rsa -noout | openssl md5 | awk '{print $2}') KCMKUBECONFIG_SERVER=$(cat $KCMKUBECONFIG | grep "server:"| awk '{print $2}') @@ -365,8 +365,8 @@ check_cert_kskubeconfig() elif [ -f $KSKUBECONFIG ] then printf "${NC}kube-scheduler kubeconfig file found, verifying the authenticity\n" - KSKUBECONFIG_SUBJECT=$(cat $KSKUBECONFIG | grep "client-certificate-data:" | awk '{print $2}' | base64 --decode | openssl x509 --text | grep "Subject: CN" | tr -d " ") - KSKUBECONFIG_ISSUER=$(cat $KSKUBECONFIG | grep "client-certificate-data:" | awk '{print $2}' | base64 --decode | openssl x509 --text | grep "Issuer: CN" | tr -d " ") + KSKUBECONFIG_SUBJECT=$(cat $KSKUBECONFIG | grep "client-certificate-data:" | awk '{print $2}' | base64 --decode | openssl x509 -text | grep "Subject: CN" | tr -d " ") + KSKUBECONFIG_ISSUER=$(cat $KSKUBECONFIG | grep "client-certificate-data:" | awk '{print $2}' | base64 --decode | openssl x509 -text | grep "Issuer: CN" | tr -d " ") KSKUBECONFIG_CERT_MD5=$(cat $KSKUBECONFIG | grep "client-certificate-data:" | awk '{print $2}' | base64 --decode | openssl x509 -noout | openssl md5 | awk '{print $2}') KSKUBECONFIG_KEY_MD5=$(cat $KSKUBECONFIG | grep "client-key-data" | awk '{print $2}' | base64 --decode | openssl rsa -noout | openssl md5 | awk '{print $2}') KSKUBECONFIG_SERVER=$(cat $KSKUBECONFIG | grep "server:"| awk '{print $2}') @@ -392,8 +392,8 @@ check_cert_adminkubeconfig() elif [ -f $ADMINKUBECONFIG ] then printf "${NC}admin kubeconfig file found, verifying the authenticity\n" - ADMINKUBECONFIG_SUBJECT=$(cat $ADMINKUBECONFIG | grep "client-certificate-data:" | awk '{print $2}' | base64 --decode | openssl x509 --text | grep "Subject: CN" | tr -d " ") - ADMINKUBECONFIG_ISSUER=$(cat $ADMINKUBECONFIG | grep "client-certificate-data:" | awk '{print $2}' | base64 --decode | openssl x509 --text | grep "Issuer: CN" | tr -d " ") + ADMINKUBECONFIG_SUBJECT=$(cat $ADMINKUBECONFIG | grep "client-certificate-data:" | awk '{print $2}' | base64 --decode | openssl x509 -text | grep "Subject: CN" | tr -d " ") + ADMINKUBECONFIG_ISSUER=$(cat $ADMINKUBECONFIG | grep "client-certificate-data:" | awk '{print $2}' | base64 --decode | openssl x509 -text | grep "Issuer: CN" | tr -d " ") ADMINKUBECONFIG_CERT_MD5=$(cat $ADMINKUBECONFIG | grep "client-certificate-data:" | awk '{print $2}' | base64 --decode | openssl x509 -noout | openssl md5 | awk '{print $2}') ADMINKUBECONFIG_KEY_MD5=$(cat $ADMINKUBECONFIG | grep "client-key-data" | awk '{print $2}' | base64 --decode | openssl rsa -noout | openssl md5 | awk '{print $2}') ADMINKUBECONFIG_SERVER=$(cat $ADMINKUBECONFIG | grep "server:"| awk '{print $2}') @@ -611,8 +611,8 @@ check_cert_worker_1_kubeconfig() elif [ -f $WORKER_1_KUBECONFIG ] then printf "${NC}worker-1 kubeconfig file found, verifying the authenticity\n" - WORKER_1_KUBECONFIG_SUBJECT=$(cat $WORKER_1_KUBECONFIG | grep "client-certificate-data:" | awk '{print $2}' | base64 --decode | openssl x509 --text | grep "Subject: CN" | tr -d " ") - WORKER_1_KUBECONFIG_ISSUER=$(cat $WORKER_1_KUBECONFIG | grep "client-certificate-data:" | awk '{print $2}' | base64 --decode | openssl x509 --text | grep "Issuer: CN" | tr -d " ") + WORKER_1_KUBECONFIG_SUBJECT=$(cat $WORKER_1_KUBECONFIG | grep "client-certificate-data:" | awk '{print $2}' | base64 --decode | openssl x509 -text | grep "Subject: CN" | tr -d " ") + WORKER_1_KUBECONFIG_ISSUER=$(cat $WORKER_1_KUBECONFIG | grep "client-certificate-data:" | awk '{print $2}' | base64 --decode | openssl x509 -text | grep "Issuer: CN" | tr -d " ") WORKER_1_KUBECONFIG_CERT_MD5=$(cat $WORKER_1_KUBECONFIG | grep "client-certificate-data:" | awk '{print $2}' | base64 --decode | openssl x509 -noout | openssl md5 | awk '{print $2}') WORKER_1_KUBECONFIG_KEY_MD5=$(cat $WORKER_1_KUBECONFIG | grep "client-key-data" | awk '{print $2}' | base64 --decode | openssl rsa -noout | openssl md5 | awk '{print $2}') WORKER_1_KUBECONFIG_SERVER=$(cat $WORKER_1_KUBECONFIG | grep "server:"| awk '{print $2}') @@ -769,4 +769,4 @@ case $value in printf "${FAILED}Exiting.... Please select the valid option either 1 or 2\n" exit 1 ;; -esac \ No newline at end of file +esac