Custom resources are extensions of the Kubernetes API. This page discusses when to add a custom resource to your Kubernetes cluster and when to use a standalone service. It describes the two methods for adding custom resources and how to choose between them. Custom resources A resource is an endpoint in the Kubernetes API that stores a collection of API objects of a certain kind; for example, the built-in pods resource contains a collection of Pod objects.

FEATURE STATE: Kubernetes v1.18 [beta] This page explains how to add Windows worker nodes to a kubeadm cluster. Before you begin A running Windows Server 2022 (or higher) instance with administrative access. A running kubeadm cluster created by kubeadm init and following the steps in the document Creating a cluster with kubeadm. Adding Windows worker nodes Note:To facilitate the addition of Windows worker nodes to a cluster, PowerShell scripts from the repository https://sigs.

This page shows how to configure quotas for API objects, including PersistentVolumeClaims and Services. A quota restricts the number of objects, of a particular type, that can be created in a namespace. You specify quotas in a ResourceQuota object. Before you begin You need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster. It is recommended to run this tutorial on a cluster with at least two nodes that are not acting as control plane hosts.

This page shows how to install a custom resource into the Kubernetes API by creating a CustomResourceDefinition. Before you begin You need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster. It is recommended to run this tutorial on a cluster with at least two nodes that are not acting as control plane hosts. If you do not already have a cluster, you can create one by using minikube or you can use one of these Kubernetes playgrounds:

This page shows how to run automated tasks using Kubernetes CronJob object. Before you begin You need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster. It is recommended to run this tutorial on a cluster with at least two nodes that are not acting as control plane hosts. If you do not already have a cluster, you can create one by using minikube or you can use one of these Kubernetes playgrounds:

This page shows how to define commands and arguments when you run a container in a Pod. Before you begin You need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster. It is recommended to run this tutorial on a cluster with at least two nodes that are not acting as control plane hosts. If you do not already have a cluster, you can create one by using minikube or you can use one of these Kubernetes playgrounds:

Creating Secret objects using kustomization.yaml file.

An Ingress is an API object that defines rules which allow external access to services in a cluster. An Ingress controller fulfills the rules set in the Ingress. This page shows you how to set up a simple Ingress which routes requests to Service 'web' or 'web2' depending on the HTTP URI. Before you begin This tutorial assumes that you are using minikube to run a local Kubernetes cluster. Visit Install tools to learn how to install minikube.

This section contains the following reference topics about nodes: the kubelet's checkpoint API a list of Articles on dockershim Removal and on Using CRI-compatible Runtimes Kubelet Device Manager API Versions Node Labels Populated By The Kubelet Local Files And Paths Used By The Kubelet Node .status information Seccomp information You can also read node reference details from elsewhere in the Kubernetes documentation, including: Node Metrics Data. CRI Pod & Container Metrics.

The kubelet is mostly a stateless process running on a Kubernetes node. This document outlines files that kubelet reads and writes. Note:This document is for informational purpose and not describing any guaranteed behaviors or APIs. It lists resources used by the kubelet, which is an implementation detail and a subject to change at any release. The kubelet typically uses the control plane as the source of truth on what needs to run on the Node, and the container runtime to retrieve the current state of containers.