concept Kubernetes API in category kubernetes

This is an excerpt from Manning's book Kubernetes in Action, Second Edition MEAP V05.
After Kubernetes is installed on the computers, you no longer need to think about individual computers when deploying applications. Regardless of the number of worker nodes in your cluster, they all become a single space where you deploy your applications. You do this using the Kubernetes API, which is provided by the Kubernetes Control Plane.
Figure 4.1 A Kubernetes cluster is configured by manipulating objects in the Kubernetes API
![]()
The Kubernetes API is the central point of interaction with the cluster, so much of this book is dedicated to explaining this API. The most important API objects are described in the following chapters, but a basic introduction to the API is presented here.

This is an excerpt from Manning's book GitOps and Kuberentes MEAP V06 epub.
kube-proxy - a network proxy that reflects services as defined in the Kubernetes API on each node and can do simple TCP, UDP, and SCTP stream forwarding.
Finally, Kubernetes Secrets can also be retrieved directly from the Kubernetes API. Suppose you had the following Secret with a password field:

This is an excerpt from Manning's book Kubernetes in Action.
I’m sure you’ll agree this is much simpler than the definition in listing 3.1. Let’s examine this descriptor in detail. It conforms to the v1 version of the Kubernetes API. The type of resource you’re describing is a pod, with the name kubia-manual. The pod consists of a single container based on the luksa/kubia image. You’ve also given a name to the container and indicated that it’s listening on port 8080.
You’ve learned about different Kubernetes resource types. But if you’re planning on developing apps that talk to the Kubernetes API, you’ll want to know the API first.