Configuring kubectl for Remote Access

In this lab you will generate a kubeconfig file for the kubectl command line utility based on the admin user credentials.

Run the commands in this lab from the same directory used to generate the admin client certificates.

The Admin Kubernetes Configuration File

Each kubeconfig requires a Kubernetes API Server to connect to. To support high availability the IP address assigned to the external load balancer fronting the Kubernetes API Servers will be used.

Generate a kubeconfig file suitable for authenticating as the admin user:

  1. {
  2.   KUBERNETES_PUBLIC_ADDRESS=$(gcloud compute addresses describe kubernetes-the-hard-way \
  3.     --region $(gcloud config get-value compute/region) \
  4.     --format 'value(address)')
  6.   kubectl config set-cluster kubernetes-the-hard-way \
  7.     --certificate-authority=ca.pem \
  8.     --embed-certs=true \
  9.     --server=https://${KUBERNETES_PUBLIC_ADDRESS}:6443
  11.   kubectl config set-credentials admin \
  12.     --client-certificate=admin.pem \
  13.     --client-key=admin-key.pem
  15.   kubectl config set-context kubernetes-the-hard-way \
  16.     --cluster=kubernetes-the-hard-way \
  17.     --user=admin
  19.   kubectl config use-context kubernetes-the-hard-way
  20. }

Verification

Check the health of the remote Kubernetes cluster:

  1. kubectl get componentstatuses

output

  1. NAME                 STATUS    MESSAGE             ERROR
  2. scheduler            Healthy   ok
  3. controller-manager   Healthy   ok
  4. etcd-0               Healthy   {"health":"true"}
  5. etcd-1               Healthy   {"health":"true"}
  6. etcd-2               Healthy   {"health":"true"}

List the nodes in the remote Kubernetes cluster:

  1. kubectl get nodes

output

  1. NAME       STATUS   ROLES    AGE     VERSION
  2. worker-0   Ready    <none>   2m30s   v1.18.6
  3. worker-1   Ready    <none>   2m30s   v1.18.6
  4. worker-2   Ready    <none>   2m30s   v1.18.6

Next: Provisioning Pod Network Routes