Kubernetes API

As explained in Learn Docker in a Month of Lunches, Second Edition

The Kubernetes API is the standardized interface for declaring, querying, and managing Kubernetes resources and application models.

The Kubernetes API lets you describe an entire application declaratively in YAML, then send that model to a cluster with kubectl. Kubernetes uses the model to coordinate containers, networking, storage, configuration, and confidential data while hiding most individual machines. section 15.1

An application model can describe these layers:

• Compute, deployed as containers. section 15.1
• Communication, implemented through cluster networking and traffic routing. section 15.1
• Storage, expressed as abstract requirements that Kubernetes can allocate or provision. section 15.1
• Configuration, including application settings and confidential data supplied to components. section 15.1

Check a local Kubernetes cluster

Enable Kubernetes in Docker Desktop, select its context, and list the cluster nodes with kubectl. This verifies that the development cluster is running. section 15.1

Figure 15.3 Modeling compute, networking, storage, and configuration in the Kubernetes API

Use the layered diagram to connect compute, networking, storage, and configuration with the Kubernetes API. section 15.1

How Learn Docker in a Month of Lunches, Second Edition covers it

How deep it goes

Defines four high-level application layers and portability, but defers detailed API mastery and production modeling.

Examples

Uses YAML application models, Docker Desktop Kubernetes, kubectl contexts, and node listings.

What it assumes

Assumes Docker familiarity while requiring further hands-on practice to become comfortable with the Kubernetes API.

What you can do after

Operate Kubernetes applications by modeling them in YAML and sending those models through kubectl.

How it connects

Connects declarative YAML with kubectl, containers, networking, storage, configuration, and the control plane.

liveBookmanning.com

Read Learn Docker in a Month of Lunches, Second Edition on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Kubernetes in Action, Second EditionThe Kubernetes API is the programmatic interface through which clients and applications query and modify Kubernetes resources and cluster state.
• 

  liveBookmanning.com
  Acing the Certified Kubernetes Administrator Exam, Second EditionThe Kubernetes API is the interface through which Kubernetes resources and cluster operations are represented and accessed.
• 

  liveBookmanning.com
  Platform Engineering on KubernetesThe Kubernetes API is the programmatic interface through which Kubernetes resources and cluster behavior are defined and managed.
• 

  liveBookmanning.com
  Effective Platform EngineeringThe Kubernetes API is the interface through which clients and components manage Kubernetes resources and cluster state.
• 

  liveBookmanning.com
  Cloud Observability in ActionThe Kubernetes API is the programmatic interface for querying and changing the state of Kubernetes resources.

Compare how 6 books explain Kubernetes API →

Related concepts

• kubectlused by · kubectl is the Kubernetes command-line client for communicating with the Kubernetes API and managing cluster resources.
• Kubernetespart of · Kubernetes is an open-source platform for orchestrating and automating the deployment, scaling, and management of containerized workloads across computing clusters.
• Kubernetes manifestused by · A Kubernetes manifest is a declarative configuration document, typically written in YAML or JSON, that specifies Kubernetes resources and their desired state.
• cloud computingused by · Cloud computing is the on-demand delivery of computing resources and services over a network from remotely managed infrastructure.
• Helmused by · Helm is a Kubernetes package manager and templating tool that defines, packages, installs, upgrades, and manages applications through charts.
• custom objecthas part · A Kubernetes custom object is an API object whose resource type and schema are defined by a custom resource definition or another extension mechanism.

This explainer was generated by Manning's knowledge graph from the text of Learn Docker in a Month of Lunches, Second Edition. The section links point to the parts of the book it draws on.