The first two chapters of this book have described how the Kubernetes API is designed, and how to access it using HTTP requests. Specifically, you have seen that resources managed by the API are organized into Group-Version-Resources, and that objects exchanged between the client and the API Server are defined as Kinds by the Kubernetes API. The chapter also shows that this data can be encoded in JSON, YAML, or Protobuf during the exchange, depending on the HTTP headers the client has set.
In the next ...
