Every interaction with Kubernetes goes through its API and needs to be authorized. That communication can be initiated through a user or a service account. All Kubernetes objects currently running inside our cluster are interacting with the API through service accounts. We won't go deep into those. Instead, we'll concentrate on the authorization of human users.
Typically, the Kubernetes API is served on a secured port. Our Minikube cluster is no exception. We can check the port from the kubectl config.
All the commands from this chapter are available in the 12-auth.sh (https://gist.github.com/vfarcic/f2c4a72a1e010f1237eea7283a9a0c11) Gist.
kubectl config view \
-o jsonpath='{.clusters[?(@.name=="minikube")].cluster.server}'
We used jsonpath to output the cluster.server entry located in the cluster with the name minikube...
