Docs
The full compiled knowledge graph, indexed by node. Each page is a static, server-rendered knowledge card with its synthesized body, provenance, and typed relationships (rendered as links to the other static pages). No runtime LLM is involved in serving this content.
Glossary terms (163)
- Add-ons — Resources that extend the functionality of Kubernetes.
- Admission Controller — A piece of code that intercepts requests to the Kubernetes API server prior to persistence of the object.
- Affinity — Rules used by the scheduler to determine where to place pods
- Aggregation Layer — The aggregation layer lets you install additional Kubernetes-style APIs in your cluster.
- Annotation — A key-value pair that is used to attach arbitrary non-identifying metadata to objects.
- API Group — A set of related paths in the Kubernetes API.
- API resource — A Kubernetes entity, representing an endpoint on the Kubernetes API server.
- API server — Control plane component that serves the Kubernetes API.
- API-initiated eviction — API-initiated eviction is the process by which you use the Eviction API to create an Eviction object that triggers graceful pod termination.
- App Container — A container used to run part of a workload. Compare with init container.
- Application Architect — A person responsible for the high-level design of an application.
- Application Developer — A person who writes an application that runs in a Kubernetes cluster.
- Applications — The layer where various containerized applications run.
- Approver — A person who can review and approve Kubernetes code contributions.
- cAdvisor — Tool that provides understanding of the resource usage and performance characteristics for containers
- Certificate — A cryptographically secure file used to validate access to the Kubernetes cluster.
- cgroup (control group) — A group of Linux processes with optional resource isolation, accounting and limits.
- CIDR — CIDR is a notation for describing blocks of IP addresses and is used heavily in various networking configurations.
- CLA (Contributor License Agreement) — Terms under which a contributor grants a license to an open source project for their contributions.
- Cloud Controller Manager — Control plane component that integrates Kubernetes with third-party cloud providers.
- Cloud Native Computing Foundation (CNCF) — The Cloud Native Computing Foundation is an organization that promotes and supports the development of cloud-native technologies.
- Cloud Provider — An organization that offers a cloud computing platform.
- Cluster — A set of worker machines, called nodes, that run containerized applications. Every cluster has at least one worker node.
- Cluster Architect — A person who designs infrastructure that involves one or more Kubernetes clusters.
- Cluster Infrastructure — The infrastructure layer provides and maintains VMs, networking, security groups and others.
- Cluster Operations — The work involved in managing a Kubernetes cluster.
- Cluster Operator — A person who configures, controls, and monitors clusters.
- Code Contributor — A person who develops and contributes code to the Kubernetes open source codebase.
- Common Expression Language — An expression language that's designed to be safe for executing user code.
- Condition — A condition represents the current state of a Kubernetes resource, providing information about whether certain aspects of the resource are true.
- ConfigMap — An API object used to store non-confidential data in key-value pairs. Can be consumed as environment variables, command-line arguments, or configuration files in a volume.
- Container — A lightweight and portable executable image that contains software and all of its dependencies.
- Container Device Interface (CDI) — A CNCF specification for describing device configuration that container runtimes apply when creating containers.
- Container Environment Variables — Container environment variables are name=value pairs that provide useful information into containers running in a Pod.
- Container Lifecycle Hooks — The lifecycle hooks expose events in the container management lifecycle and let the user run code when the events occur.
- Container network interface (CNI) — Container network interface (CNI) plugins are a type of Network plugin that adheres to the appc/CNI specification.
- Container Runtime — The container runtime is the software that is responsible for running containers.
- Container Runtime Interface (CRI) — Protocol for communication between the kubelet and the local container runtime.
- Container Storage Interface (CSI) — The Container Storage Interface (CSI) defines a standard interface to expose storage systems to containers.
- containerd — A container runtime with an emphasis on simplicity, robustness and portability
- Contributor — Someone who donates code, documentation, or their time to help the Kubernetes project or community.
- Control Plane — The container orchestration layer that exposes the API and interfaces to define, deploy, and manage the lifecycle of containers.
- Controller — A control loop that watches the shared state of the cluster through the apiserver and makes changes attempting to move the current state towards the desired state.
- CRI-O — A lightweight container runtime specifically for Kubernetes
- CronJob — A repeating task (a Job) that runs on a regular schedule.
- CustomResourceDefinition — Custom code that defines a resource to add to your Kubernetes API server without building a complete custom server.
- DaemonSet — Ensures a copy of a Pod is running across a set of nodes in a cluster.
- Data Plane — The layer that provides capacity such as CPU, memory, network, and storage so that the containers can run and connect to a network.
- Deployment — Manages a replicated application on your cluster.
- Developer (disambiguation) — May refer to: Application Developer, Code Contributor, or Platform Developer.
- Device — Any resource that's directly or indirectly attached your cluster's nodes, like GPUs or circuit boards.
- Device Plugin — Software extensions to let Pods access devices that need vendor-specific initialization or setup
- DeviceClass — A category of devices in the cluster. Users can claim specific devices in a DeviceClass.
- Disruption — An event that leads to Pod(s) going out of service
- Docker — Docker is a software technology providing operating-system-level virtualization also known as containers.
- Dockershim — A component of Kubernetes v1.23 and earlier, which allows Kubernetes system components to communicate with Docker Engine.
- Downstream (disambiguation) — May refer to: code in the Kubernetes ecosystem that depends upon the core Kubernetes codebase or a forked repo.
- Downward API — A mechanism to expose Pod and container field values to code running in a container.
- Drain — Safely evicts Pods from a Node to prepare for maintenance or removal.
- Duration — A string value representing an amount of time.
- Dynamic Resource Allocation — A Kubernetes feature for requesting and sharing resources, like hardware accelerators, among Pods.
- Dynamic Volume Provisioning — Allows users to request automatic creation of storage Volumes.
- Endpoints — (Deprecated) API representing endpoints of a Service
- EndpointSlice — EndpointSlices track the IP addresses of Pods for Services.
- Ephemeral Container — A type of container type that you can temporarily run inside a Pod
- etcd — Consistent and highly-available key value store used as backing store of Kubernetes for all cluster data.
- Event — Kubernetes objects that describe some state change in the cluster.
- Eviction — Process of terminating one or more Pods on Nodes
- Extensions — Extensions are software components that extend and deeply integrate with Kubernetes to support new types of hardware.
- Feature gate — A way to control whether or not a particular Kubernetes feature is enabled.
- Finalizer — A namespaced key that tells Kubernetes to wait until specific conditions are met before it fully deletes an object marked for deletion.
- FlexVolume — FlexVolume is a deprecated interface for creating out-of-tree volume plugins. The {{< glossary_tooltip text="Container Storage Interface" term_id="csi" >}} is a newer interface that addresses several problems with FlexVolume.
- Garbage Collection — A collective term for the various mechanisms Kubernetes uses to clean up cluster resources.
- Gateway API — An API for modeling service networking in Kubernetes.
- Glossary — A centralized repository of terms and definitions used within a project or organization.
- Group Version Resource — The API group, API version and name of a Kubernetes API.
- Helm Chart — A package of pre-configured Kubernetes configurations that can be managed with the Helm tool.
- Horizontal Pod Autoscaler — Object that automatically scales the number of pod replicas based on targeted resource utilization or custom metric targets.
- HostAliases — A HostAliases is a mapping between the IP address and hostname to be injected into a Pod's hosts file.
- Image — Stored instance of a container that holds a set of software needed to run an application.
- Immutable Infrastructure — Immutable Infrastructure refers to computer infrastructure (virtual machines, containers, network appliances) that cannot be changed once deployed
- Ingress — An API object that manages external access to the services in a cluster, typically HTTP.
- Init Container — One or more initialization containers that must run to completion before any app containers run.
- Istio — An open platform (not Kubernetes-specific) that provides a uniform way to integrate microservices, manage traffic flow, enforce policies, and aggregate telemetry data.
- Job — A finite or batch task that runs to completion.
- JSON Web Token (JWT) — A means of representing claims to be transferred between two parties.
- kOps (Kubernetes Operations) — kOps will not only help you create, destroy, upgrade and maintain production-grade, highly available, Kubernetes cluster, but it will also provision the necessary cloud infrastructure.
- kube-controller-manager — Control Plane component that runs controller processes.
- kube-proxy — `kube-proxy` is a network proxy that runs on each node in the cluster.
- kube-scheduler — Control plane component that watches for newly created pods with no assigned node, and selects a node for them to run on.
- Kubeadm — A tool for quickly installing Kubernetes and setting up a secure cluster.
- Kubectl — A command line tool for communicating with a Kubernetes cluster.
- Kubelet — An agent that runs on each node in the cluster. It makes sure that containers are running in a pod.
- Kubernetes API — The application that serves Kubernetes functionality through a RESTful interface and stores the state of the cluster.
- Label — Tags objects with identifying attributes that are meaningful and relevant to users.
- LimitRange — Provides constraints to limit resource consumption per Containers or Pods in a namespace.
- Logging — Logs are the list of events that are logged by cluster or application.
- Managed Service — A software offering maintained by a third-party provider.
- Manifest — A serialized specification of one or more Kubernetes API objects.
- Master — Legacy term, used as synonym for nodes running the control plane.
- Member — A continuously active contributor in the K8s community.
- Minikube — A tool for running Kubernetes locally.
- Mirror Pod — An object in the API server that tracks a static pod on a kubelet.
- Mixed Version Proxy (MVP) — Feature that lets a kube-apiserver proxy a resource request to a different peer API server.
- Name — A client-provided string that refers to an object in a resource URL, such as `/api/v1/pods/some-name`.
- Namespace — An abstraction used by Kubernetes to support isolation of groups of resources within a single cluster.
- Network Policy — A specification of how groups of Pods are allowed to communicate with each other and with other network endpoints.
- Node — A node is a worker machine in Kubernetes.
- Node-pressure eviction — Node-pressure eviction is the process by which the kubelet proactively fails pods to reclaim resources on nodes.
- Object — An entity in the Kubernetes system, representing part of the state of your cluster.
- Operator pattern — A specialized controller used to manage a custom resource
- Persistent Volume — API object that represents a piece of storage in the cluster.
- Persistent Volume Claim — Claims storage resources defined in a PersistentVolume so that it can be mounted as a volume in a container.
- Platform Developer — A person who customizes the Kubernetes platform to fit the needs of their project.
- Pod — A Pod represents a set of running containers in your cluster.
- Pod Disruption — The process by which Pods on Nodes are terminated either voluntarily or involuntarily.
- Pod Disruption Budget — An object that limits the number of Pods of a replicated application that are down simultaneously from voluntary disruptions.
- Pod Lifecycle — The sequence of states through which a Pod passes during its lifetime.
- Pod Priority — Pod Priority indicates the importance of a Pod relative to other Pods.
- Pod Security Policy — Removed API that enforced Pod security restrictions.
- PodGroup — A PodGroup represents a set of Pods with common scheduling policy and constraints.
- PodTemplate — A template for creating Pods.
- Preemption — Preemption logic in Kubernetes helps a pending Pod to find a suitable Node by evicting low priority Pods existing on that Node.
- PriorityClass — A mapping from a class name to the scheduling priority that a Pod should have.
- Probe — A check performed periodically by the kubelet on a container in a Pod.
- Proxy — An application acting as an intermediary between clients and servers
- QoS Class — QoS Class (Quality of Service Class) provides a way for Kubernetes to classify pods within the cluster into several classes and make decisions about scheduling and eviction.
- Quantity — A whole-number representation of small or large numbers using SI suffixes.
- RBAC (Role-Based Access Control) — Manages authorization decisions, allowing admins to dynamically configure access policies through the Kubernetes API.
- Replica — Replicas are copies of pods, ensuring availability, scalability, and fault tolerance by maintaining identical instances.
- ReplicaSet — ReplicaSet ensures that a specified number of Pod replicas are running at one time
- ReplicationController — A (deprecated) API object that manages a replicated application.
- Resource (infrastructure) — A defined amount of infrastructure available for consumption (CPU, memory, etc).
- ResourceClaim — Describes the resources that a workload needs, such as devices. ResourceClaims can request devices from DeviceClasses.
- ResourceClaimTemplate — Defines a template for Kubernetes to create ResourceClaims. Used to provide per-Pod or per-PodGroup access to separate, similar resources.
- ResourceQuota — Provides constraints that limit aggregate resource consumption per namespace.
- ResourceSlice — Represents one or more infrastructure resources, like devices, in a pool of similar resources.
- Reviewer — A person who reviews code for quality and correctness on some part of the project.
- Secret — Stores sensitive information, such as passwords, OAuth tokens, and ssh keys.
- Security Context — The securityContext field defines privilege and access control settings for a Pod or container.
- Selector — Allows users to filter a list of resources based on labels.
- Service — A way to expose an application running on a set of Pods as a network service.
- Service Catalog — A former extension API that enabled applications running in Kubernetes clusters to easily use external managed software offerings, such as a datastore service offered by a cloud provider.
- ServiceAccount — Provides an identity for processes that run in a Pod.
- Shuffle-sharding — A technique for assigning requests to queues that provides better isolation than hashing modulo the number of queues.
- Sidecar Container — An auxilliary container that stays running throughout the lifecycle of a Pod.
- SIG (special interest group) — Community members who collectively manage an ongoing piece or aspect of the larger Kubernetes open source project.
- Spec — Field in Kubernetes manifests that defines the desired state or configuration.
- StatefulSet — A StatefulSet manages deployment and scaling of a set of Pods, with durable storage and persistent identifiers for each Pod.
- Static Pod — A pod managed directly by the kubelet daemon on a specific node.
- Storage Class — A StorageClass provides a way for administrators to describe different available storage types.
- Subject Alternative Name — An X.509 certificate extension to identify what hostname or IP address the certificate applies to.
- sysctl — An interface for getting and setting Unix kernel parameters
- Taint — A core object consisting of three required properties: key, value, and effect. Taints prevent the scheduling of pods on nodes or node groups.
- Toleration — A core object consisting of three required properties: key, value, and effect. Tolerations enable the scheduling of pods on nodes or node groups that have a matching taint.
- UID — A Kubernetes systems-generated string to uniquely identify objects.
- Upstream (disambiguation) — May refer to: core Kubernetes or the source repo from which a repo was forked.
- user namespace — A Linux kernel feature to emulate superuser privilege for unprivileged users.
- Volume — A directory containing data, accessible to the containers in a pod.
- Volume Plugin — A Volume Plugin enables integration of storage within a Pod.
- Watch — A verb that is used to track changes to an object in Kubernetes as a stream.
- WG (working group) — Facilitates the discussion and/or implementation of a short-lived, narrow, or decoupled project for a committee, SIG, or cross-SIG effort.
- Workload — A workload is an application running on Kubernetes.
Documentation pages (1469)
- _index
- _index
- _index
- _index
- _index
- _index
- _index
- _index
- _index
- _index
- About cgroup v2
- Accelerators — Accelerators is a feature gate that enables support for accelerators, such as GPUs and TPUs.
- Access Applications in a Cluster — Configure load balancing, port forwarding, or setup firewall or DNS configurations to access applications in a cluster.
- Access Clusters Using the Kubernetes API
- Access DRA Device Metadata
- Access Services Running on Clusters
- Accessing Clusters
- Accessing the Kubernetes API from a Pod
- Adding entries to Pod /etc/hosts with HostAliases
- Adding Linux worker nodes
- Adding Windows worker nodes
- Administer a Cluster — Learn common tasks for administering a cluster.
- Administration with kubeadm — Administer your cluster using kubeadm, a tool for bootstrapping and managing Kubernetes clusters.
- Admission Control in Kubernetes
- Admission Webhook Good Practices — Recommendations for designing and deploying admission webhooks in Kubernetes.
- Admissionregistration — Admissionregistration in Kubernetes refers to the process of validating and mutating API requests before they are processed.
- AdmissionWebhookMatchConditions — A feature gate that enables or disables the Admission Webhook Match Conditions in Kubernetes.
- Adopting Sidecar Containers
- Advanced Pod Configuration
- AdvancedAuditing — Enables advanced auditing features in Kubernetes.
- Advertise Extended Resources for a Node
- AffinityInAnnotations — AffinityInAnnotations is a feature gate that enables or disables the use of affinity in annotations.
- AggregatedDiscoveryEndpoint — A feature gate that enables or disables the aggregated discovery endpoint.
- Allocate Devices to Workloads with DRA
- AllowDNSOnlyNodeCSR — AllowDNSOnlyNodeCSR is a feature gate that allows DNS-only Node Certificate Signing Requests (CSRs) to be processed.
- AllowExtTrafficLocalEndpoints — AllowExtTrafficLocalEndpoints is a feature gate that enables or disables allowing external traffic to local endpoints.
- AllowInsecureBackendProxy — Enables insecure backend proxy connections.
- AllowInsecureKubeletCertificateSigningRequests — AllowInsecureKubeletCertificateSigningRequests is a feature gate that controls whether Kubelet certificate signing requests are allowed to be insecure.
- AllowParsingUserUIDFromCertAuth — Allows parsing of user UID from certificate authentication.
- AllowServiceLBStatusOnNonLB — A feature gate that allows setting Service LB status on non-LB services.
- AllowUnsafeMalformedObjectDeletion — Enables the deletion of malformed objects without validation checks.
- Annotations
- AnonymousAuthConfigurableEndpoints — AnonymousAuthConfigurableEndpoints is a feature gate that controls whether anonymous authentication is allowed on configurable endpoints.
- AnyVolumeDataSource — A feature gate that allows using any volume as a data source.
- API Access Control
- API Groups — Kubernetes API groups and their served versions.
- API Overview
- API Priority and Fairness
- API-initiated Eviction
- Apiextensions — Apiextensions is a Kubernetes API that allows users to manage and extend the Kubernetes cluster's configuration.
- APIGroup — APIGroup contains the name, the supported versions, and the preferred version of a group.
- APIListChunking — A feature gate that enables API list chunking.
- APIPriorityAndFairness — APIPriorityAndFairness is a feature gate that enables API priority and fairness.
- Apiregistration — Apiregistration in Kubernetes refers to the process of registering and managing API servers.
- APIResource — APIResource specifies the name of a resource and whether it is namespaced.
- APIResponseCompression — APIResponseCompression is a feature gate that enables compression of API responses.
- APISelfSubjectReview — APISelfSubjectReview enables self-review of API requests.
- APIServerIdentity — A feature gate that allows the API server to identify itself.
- Apiserverinternal — Apiserverinternal is an internal API of Kubernetes.
- APIServerTracing — APIServerTracing is a feature gate that enables tracing for the API server.
- APIService — APIService represents a server for a particular GroupVersion. Name must be "version.group".
- APIServingWithRoutine — Enables serving APIs with the Routine framework in Kubernetes.
- APIVersions — APIVersions lists the versions that are available, to allow clients to discover the API at /api, which is the root path of the legacy v1 API.
- AppArmor — AppArmor is a Linux kernel feature that provides mandatory access control (MAC) to restrict an application's capabilities.
- AppArmorFields — AppArmorFields is a feature gate that enables AppArmor fields.
- Application Security Checklist — Baseline guidelines around ensuring application security on Kubernetes, aimed at application developers
- Apply Pod Security Standards at the Cluster Level
- Apply Pod Security Standards at the Namespace Level
- Apps — Apps is a collection of Kubernetes API objects related to application management.
- Articles on dockershim Removal and on Using CRI-compatible Runtimes
- Assign CPU Resources to Containers and Pods
- Assign Devices to Pods and Containers — Assign infrastructure resources to your Kubernetes workloads.
- Assign Extended Resources to a Container
- Assign Memory Resources to Containers and Pods
- Assign Pod-level CPU and memory resources
- Assign Pods to Nodes
- Assign Pods to Nodes using Node Affinity
- Assigning Pods to Nodes
- AtomicFIFO — The AtomicFIFO feature gate enables or disables the use of atomic FIFO (First-In-First-Out) for persistent volumes.
- Attach Handlers to Container Lifecycle Events
- AttachVolumeLimit — AttachVolumeLimit is a feature gate that controls whether attaching volumes to pods is allowed.
- Audit Annotations
- Auditing
- Authenticating
- Authenticating with Bootstrap Tokens
- Authorization — Details of Kubernetes authorization mechanisms and supported authorization modes.
- AuthorizeNodeWithSelectors — A feature gate for enabling Authorize Node with Selectors.
- AuthorizePodWebsocketUpgradeCreatePermission
- AuthorizeWithSelectors
- Automatic Cleanup for Finished Jobs — A time-to-live mechanism to clean up old Jobs that have finished execution.
- Autoscale the DNS Service in a Cluster
- Autoscaling — Autoscaling allows Kubernetes to automatically adjust the number of replicas for a deployment.
- Autoscaling Workloads — With autoscaling, you can automatically update your workloads in one way or another. This allows your cluster to react to changes in resource demand more elastically and efficiently.
- Available Documentation Versions — Multiple versions of documentation are available for Kubernetes.
- BalanceAttachedNodeVolumes — Enables balancing of attached node volumes.
- bash auto-completion on Linux — Some optional configuration for bash auto-completion on Linux.
- bash auto-completion on macOS — Some optional configuration for bash auto-completion on macOS.
- BasicDevice — BasicDevice defines one device instance.
- Batch — Batch in Kubernetes refers to the execution of batch jobs, which are applications that run to completion.
- Best practices — Establishing best practices is essential for a smooth Kubernetes experience.
- Binding — Binding ties one object to another; for example, a pod is bound to a node by a scheduler.
- BlockVolume — A feature gate that enables block volumes in Kubernetes.
- Bootstrapping clusters with kubeadm — Bootstrapping clusters with kubeadm involves using a tool to automate the installation and configuration of a Kubernetes cluster.
- BoundServiceAccountTokenVolume — A feature gate for enabling or disabling the use of bound service account token volumes.
- BtreeWatchCache — BtreeWatchCache is a feature gate that enables or disables B-tree watch cache.
- Building a Basic DaemonSet
- CBORServingAndStorage — CBORServingAndStorage is a feature gate that enables the use of CBOR (Concise Binary Object Representation) for serving and storing data.
- Certificate Management with kubeadm
- Certificates — Certificates are used to authenticate and authorize entities in Kubernetes.
- Certificates — Certificates are a feature in Kubernetes that enables secure communication between pods and services within a cluster.
- Certificates and Certificate Signing Requests
- CertificateSigningRequest — CertificateSigningRequest objects provide a mechanism to obtain x509 certificates by submitting a certificate signing request, and having it asynchronously approved and issued. Kubelets use this API to obtain: 1. client certificates to authenticate to kube-apiserver (with the "kubernetes.io/kube-apiserver-client-kubelet" signerName). 2. serving certificates for TLS endpoints kube-apiserver can connect to securely (with the "kubernetes.io/kubelet-serving" signerName). This API can be used to request client certificates to authenticate to kube-apiserver (with the "kubernetes.io/kube-apiserver-client" signerName), or to obtain certificates from custom non-Kubernetes signers.
- Change the Access Mode of a PersistentVolume to ReadWriteOncePod
- Change the default StorageClass
- Change the Reclaim Policy of a PersistentVolume
- ChangeContainerStatusOnKubeletRestart — Changes the container status on Kubelet restart.
- Changing the Container Runtime on a Node from Docker Engine to containerd
- Changing The Kubernetes Package Repository
- Check whether dockershim removal affects you
- ClearingNominatedNodeNameAfterBinding — ClearingNominatedNodeNameAfterBinding is a feature that clears the nominated node name after pod binding.
- Client Authentication (v1)
- Client Authentication (v1beta1)
- Client Libraries
- Cloud Controller Manager
- Cloud Controller Manager Administration
- Cloud Native Security and Kubernetes — Concepts for keeping your cloud native workload secure.
- CloudControllerManagerWatchBasedRoutesReconciliation
- CloudControllerManagerWebhook — Enables the Cloud Controller Manager webhook, allowing it to manage cluster resources.
- CloudDualStackNodeIPs — CloudDualStackNodeIPs is a feature gate that supports dual-stack node IPs in cloud environments.
- Cluster Administration — Lower-level detail relevant to creating or administering a Kubernetes cluster.
- Cluster Architecture — The architectural concepts behind Kubernetes.
- Cluster Management — Cluster Management involves the administration, maintenance, and scaling of Kubernetes clusters.
- Cluster Networking
- ClusterRole — ClusterRole is a cluster level, logical grouping of PolicyRules that can be referenced as a unit by a RoleBinding or ClusterRoleBinding.
- ClusterRoleBinding — ClusterRoleBinding references a ClusterRole, but not contain it. It can reference a ClusterRole in the global namespace, and adds who information via Subject.
- ClusterTrustBundle — ClusterTrustBundle is a cluster-scoped container for X.509 trust anchors (root certificates). ClusterTrustBundle objects are considered to be readable by any authenticated user in the cluster, because they can be mounted by pods using the `clusterTrustBundle` projection. All service accounts have read access to ClusterTrustBundles by default. Users who only have namespace-level access to a cluster can read ClusterTrustBundles by impersonating a serviceaccount that they have access to. It can be optionally associated with a particular assigner, in which case it contains one valid set of trust anchors for that signer. Signers may have multiple associated ClusterTrustBundles; each is an independent set of trust anchors for that signer. Admission control is used to enforce that only users with permissions on the signer can create or modify the corresponding bundle.
- ClusterTrustBundle — ClusterTrustBundle is a feature that enables cluster-wide certificate rotation and renewal.
- ClusterTrustBundleProjection — A feature gate for enabling Cluster Trust Bundle Projection.
- Coarse Parallel Processing Using a Work Queue
- Command line tool (kubectl)
- Common Expression Language in Kubernetes
- Communicate Between Containers in the Same Pod Using a Shared Volume
- Communication between Nodes and the Control Plane
- Compatibility Version For Kubernetes Control Plane Components
- Component tools — Component tools are used to manage and interact with Kubernetes clusters.
- ComponentFlagz — A feature gate for enabling or disabling specific Kubernetes components.
- ComponentSLIs — A feature gate that enables component-level service level indicators (SLIs).
- ComponentStatus — ComponentStatus (and ComponentStatusList) holds the cluster validation info. Deprecated: This API is deprecated in v1.19+
- ComponentStatusz — A feature gate that allows you to display component status in the Kubernetes dashboard.
- Compute, Storage, and Networking Extensions
- Concepts — Kubernetes concepts are fundamental building blocks for cluster management.
- ConcurrentWatchObjectDecode — ConcurrentWatchObjectDecode is a feature gate that enables concurrent decoding of watch objects.
- Condition — Condition contains details for one aspect of the current state of this API Resource.
- ConfigMap — ConfigMap holds configuration data for pods to consume.
- ConfigMaps
- ConfigurableFSGroupPolicy — A feature gate that allows configuring the File System Group Policy for pods.
- Configuration — Resources that Kubernetes provides for configuring Pods.
- Configuration — Configuration refers to the process of setting up and managing Kubernetes resources.
- Configuration APIs — A collection of configuration APIs and guides.
- Configure a kubelet image credential provider
- Configure a Pod Quota for a Namespace — Restrict how many Pods you can create within a namespace.
- Configure a Pod to Use a ConfigMap
- Configure a Pod to Use a PersistentVolume for Storage
- Configure a Pod to Use a Projected Volume for Storage
- Configure a Pod to Use a Volume for Storage
- Configure a Security Context for a Pod or Container
- Configure Access to Multiple Clusters
- Configure Certificate Rotation for the Kubelet
- Configure Default CPU Requests and Limits for a Namespace — Define a default CPU resource limits for a namespace, so that every new Pod in that namespace has a CPU resource limit configured.
- Configure Default Memory Requests and Limits for a Namespace — Define a default memory resource limit for a namespace, so that every new Pod in that namespace has a memory resource limit configured.
- Configure DNS for a Cluster — Configure DNS for a Cluster to enable name resolution and communication between pods.
- Configure GMSA for Windows Pods and containers
- Configure Liveness, Readiness and Startup Probes
- Configure Memory and CPU Quotas for a Namespace — Define overall memory and CPU resource limits for a namespace.
- Configure Minimum and Maximum CPU Constraints for a Namespace — Define a range of valid CPU resource limits for a namespace, so that every new Pod in that namespace falls within the range you configure.
- Configure Minimum and Maximum Memory Constraints for a Namespace — Define a range of valid memory resource limits for a namespace, so that every new Pod in that namespace falls within the range you configure.
- Configure Multiple Schedulers
- Configure Pod Initialization
- Configure Pods and Containers — Perform common configuration tasks for Pods and containers.
- Configure Quality of Service for Pods
- Configure Quotas for API Objects
- Configure RunAsUserName for Windows pods and containers
- Configure Service Accounts for Pods
- Configure the Aggregation Layer
- Configuring a cgroup driver
- Configuring each kubelet in your cluster using kubeadm
- Configuring Redis using a ConfigMap
- Configuring swap memory on Kubernetes nodes
- Connect a Frontend to a Backend Using Services
- Connecting Applications with Services
- Considerations for large clusters
- ConsistentHTTPGetHandlers — A feature gate that enables consistent HTTP GET handlers for Kubernetes components.
- ConsistentListFromCache
- ConstrainedImpersonation — The ConstrainedImpersonation feature gate enables constrained impersonation in Kubernetes.
- Container Environment
- Container Lifecycle Hooks
- Container Runtime Interface (CRI)
- Container Runtimes
- ContainerCheckpoint — ContainerCheckpoint is a feature gate that enables container checkpointing.
- ContainerRestartRules — A feature gate that allows you to control whether containers are restarted when a node is rebooted.
- Containers — Technology for packaging an application along with its runtime dependencies.
- ContainerStopSignals — Allows sending stop signals to containers.
- ContextualLogging — Enables contextual logging for Kubernetes components.
- Control CPU Management Policies on the Node
- Control Memory Management Policies on a Node
- Control Topology Management Policies on a node
- ControllerManagerLeaderMigration — ControllerManagerLeaderMigration is a feature gate that enables or disables the leader migration functionality in the Controller Manager.
- ControllerManagerReleaseLeaderElectionLockOnExit — The ControllerManagerReleaseLeaderElectionLockOnExit feature gate enables release of the leader election lock on exit in Kubernetes.
- ControllerRevision — ControllerRevision implements an immutable snapshot of state data. Clients are responsible for serializing and deserializing the objects that contain their internal state. Once a ControllerRevision has been successfully created, it can not be updated. The API Server will fail validation of all requests that attempt to mutate the Data field. ControllerRevisions may, however, be deleted. Note that, due to its use by both the DaemonSet and StatefulSet controllers for update and rollback, this object is beta. However, it may be subject to name and representation changes in future releases, and clients should not depend on its stability. It is primarily for internal use by controllers.
- Controllers
- Controlling Access to the Kubernetes API
- Coordinated Leader Election
- CoordinatedLeaderElection — CoordinatedLeaderElection is a feature gate that enables coordinated leader election in Kubernetes.
- Coordination — Coordination is a component of Kubernetes that manages distributed systems.
- Core — Core is a set of APIs in Kubernetes that provide basic functionality.
- CPUManager — CPU Manager is a feature gate that enables the CPU manager to manage CPU resources for pods.
- CPUManagerPolicyAlphaOptions — CPUManagerPolicyAlphaOptions is a feature gate that enables CPU manager policy alpha options.
- CPUManagerPolicyBetaOptions — A feature gate for CPU manager policy beta options.
- CPUManagerPolicyOptions — CPUManagerPolicyOptions is a feature gate for managing CPU resources in Kubernetes.
- CRDObservedGenerationTracking — CRD Observed Generation Tracking is a feature gate that enables the tracking of observed generations for Custom Resource Definitions (CRDs).
- CRDValidationRatcheting — CRDValidationRatcheting enables validation of Custom Resource Definitions (CRDs).
- Create a Cluster — Create a Cluster to deploy and manage your app's containers, ensuring efficient resource utilization and high availability.
- Create a Windows HostProcess Pod
- Create an External Load Balancer
- Create static Pods
- Creating a cluster with kubeadm
- Creating Highly Available Clusters with kubeadm
- CRI Pod & Container Metrics — Collection of Pod & Container metrics via the CRI.
- CRIContainerLogRotation — CRIContainerLogRotation is a feature gate that enables container log rotation for CRI (Container Runtime Interface) containers.
- CRIListStreaming — CRIListStreaming is a feature gate that enables streaming of CRI (Container Runtime Interface) list responses.
- CronJob — A CronJob starts one-time Jobs on a repeating schedule.
- CronJob — CronJob represents the configuration of a single cron job.
- CronJobControllerV2 — CronJobControllerV2 is a feature gate that enables the new CronJob controller.
- CronJobsScheduledAnnotation — CronJobsScheduledAnnotation is a feature gate that enables scheduled cron jobs.
- CronJobTimeZone — CronJobTimeZone is a feature gate that allows setting the time zone for CronJobs.
- CrossNamespaceVolumeDataSource — A feature gate that enables cross-namespace volume data sources.
- CSI Volume Cloning
- CSIBlockVolume — CSIBlockVolume is a feature that enables CSI (Container Storage Interface) support for block volumes.
- CSIDriver — CSIDriver captures information about a Container Storage Interface (CSI) volume driver deployed on the cluster. Kubernetes attach detach controller uses this object to determine whether attach is required. Kubelet uses this object to determine whether pod information needs to be passed on mount. CSIDriver objects are non-namespaced.
- CSIDriverRegistry — A feature gate that enables the CSI driver registry.
- CSIInlineVolume — CSIInlineVolume is a feature gate that enables inline volume creation for CSI drivers.
- CSIMigration — CSIMigration is a feature gate that enables CSI migration.
- CSIMigrationAWS
- CSIMigrationAWSComplete — CSIMigrationAWSComplete is a feature gate that enables the completion of CSI migration on AWS.
- CSIMigrationAzureDisk — The CSIMigrationAzureDisk feature gate enables or disables the migration of CSI (Container Storage Interface) drivers to Azure Disk.
- CSIMigrationAzureDiskComplete — CSIMigrationAzureDiskComplete is a feature gate that enables the migration of Azure Disk Persistent Volumes to CSI (Container Storage Interface) volumes.
- CSIMigrationAzureFile — A feature gate that enables or disables the CSI migration for Azure File volumes in Kubernetes.
- CSIMigrationAzureFileComplete — CSIMigrationAzureFileComplete is a feature gate that controls the migration of CSI drivers to Azure File Complete.
- CSIMigrationGCE — CSIMigrationGCE is a feature gate that enables migration of CSI drivers to use GCE.
- CSIMigrationGCEComplete — A feature gate that enables complete CSI migration on GCE.
- CSIMigrationOpenStack — A feature gate for CSI migration on OpenStack.
- CSIMigrationOpenStackComplete — CSIMigrationOpenStackComplete is a feature gate that enables the completion of CSI migration for OpenStack.
- CSIMigrationPortworx — CSIMigrationPortworx is a feature gate that enables CSI migration for Portworx storage.
- CSIMigrationRBD — Feature gate for enabling CSI migration from RBD.
- CSIMigrationvSphere — A feature gate related to vSphere CSI migration.
- CSIMigrationvSphereComplete — A feature gate that enables the complete migration of CSI drivers to vSphere.
- CSINode — CSINode holds information about all CSI drivers installed on a node. CSI drivers do not need to create the CSINode object directly. As long as they use the node-driver-registrar sidecar container, the kubelet will automatically populate the CSINode object for the CSI driver as part of kubelet plugin registration. CSINode has the same name as a node. If the object is missing, it means either there are no CSI Drivers available on the node, or the Kubelet version is low enough that it doesn't create this object. CSINode has an OwnerReference that points to the corresponding node object.
- CSINodeExpandSecret — CSINodeExpandSecret is a feature gate that controls the expansion of CSI secrets.
- CSINodeInfo — CSINodeInfo is a feature gate that enables or disables the collection of CSI node information.
- CSIPersistentVolume — CSIPersistentVolume is a feature gate that enables the use of CSI (Container Storage Interface) persistent volumes.
- CSIServiceAccountToken — A feature gate that enables the use of service account tokens in CSI drivers.
- CSIServiceAccountTokenSecrets — CSIServiceAccountTokenSecrets is a feature gate that enables CSI service account token secrets.
- CSIStorageCapacity — CSIStorageCapacity stores the result of one CSI GetCapacity call. For a given StorageClass, this describes the available capacity in a particular topology segment. This can be used when considering where to instantiate new PersistentVolumes. For example this can express things like: - StorageClass "standard" has "1234 GiB" available in "topology.kubernetes.io/zone=us-east1" - StorageClass "localssd" has "10 GiB" available in "kubernetes.io/hostname=knode-abc123" The following three cases all imply that no capacity is available for a certain combination: - no object exists with suitable topology and storage class name - such an object exists, but the capacity is unset - such an object exists, but the capacity is zero The producer of these objects can decide which approach is more suitable. They are consumed by the kube-scheduler when a CSI driver opts into capacity-aware scheduling with CSIDriverSpec.StorageCapacity. The scheduler compares the MaximumVolumeSize against the requested size of pending volumes to filter out unsuitable nodes. If MaximumVolumeSize is unset, it falls back to a comparison against the less precise Capacity. If that is also unset, the scheduler assumes that capacity is insufficient and tries some other node.
- CSIStorageCapacity — Enables CSI Storage Capacity feature.
- CSIVolumeFSGroupPolicy — CSIVolumeFSGroupPolicy is a feature gate that enables CSI volume's fsGroup policy.
- CSIVolumeHealth — The CSIVolumeHealth feature gate enables CSI volume health checks in Kubernetes.
- CSRDuration — A feature gate that allows you to configure the duration of certificate signing requests (CSRs).
- Custom Resources
- CustomCPUCFSQuotaPeriod — CustomCPUCFSQuotaPeriod is a feature gate that enables custom CPU and file system quota periods.
- Customizing components with the kubeadm API
- Customizing DNS Service
- CustomPodDNS — Custom Pod DNS allows for custom DNS configuration in pods.
- CustomResourceDefaulting — CustomResourceDefaulting is a feature gate that allows default values for custom resources.
- CustomResourceDefinition — CustomResourceDefinition represents a resource that should be exposed on the API server. Its name MUST be in the format <.spec.name>.<.spec.group>.
- CustomResourceFieldSelectors — CustomResourceFieldSelectors is a feature gate that enables support for custom resource field selectors in Kubernetes.
- CustomResourcePublishOpenAPI — CustomResourcePublishOpenAPI is a feature gate that enables custom resources to be published as OpenAPI documents.
- CustomResourceSubresources — CustomResourceSubresources is a feature gate that enables subresource management for custom resources.
- CustomResourceValidation — CustomResourceValidation is a feature gate that enables custom resource validation.
- CustomResourceValidationExpressions — Enables custom validation expressions for Custom Resources.
- CustomResourceWebhookConversion — CustomResourceWebhookConversion is a feature gate that enables conversion of custom resources to webhooks.
- DaemonSet — A DaemonSet defines Pods that provide node-local facilities. These might be fundamental to the operation of your cluster, such as a networking helper tool, or be part of an add-on.
- DaemonSet — DaemonSet represents the configuration of a daemon set.
- DaemonSetUpdateSurge — DaemonSetUpdateSurge is a feature gate that allows for daemon set updates.
- Debug a StatefulSet
- Debug cluster — A debug cluster in Kubernetes is a special type of cluster for debugging purposes.
- Debug Init Containers
- Debug Pods
- Debug Running Pods
- Debug Services
- Debugging DNS Resolution
- Debugging Kubernetes nodes with crictl
- Debugging Kubernetes Nodes With Kubectl
- Declarative API Validation
- Declarative Management of Kubernetes Objects Using Configuration Files
- Declarative Management of Kubernetes Objects Using Kustomize
- DeclarativeValidation
- DeclarativeValidationBeta
- DeclarativeValidationTakeover
- Declare Network Policy
- Decrypt Confidential Data that is Already Encrypted at Rest
- DefaultHostNetworkHostPortsInPodTemplates — DefaultHostNetworkHostPortsInPodTemplates is a feature gate that controls the default host network and host ports in pod templates.
- DefaultPodTopologySpread — A feature gate that enables or disables the default pod topology spread.
- Define a Command and Arguments for a Container
- Define Dependent Environment Variables
- Define Environment Variable Values Using An Init Container
- Define Environment Variables for a Container
- Definitions — Definitions is a collection of Kubernetes API object definitions.
- DelegateFSGroupToCSIDriver — DelegateFSGroupToCSIDriver is a feature gate that enables the CSI driver to delegate the file system group (FSGroup) to pods.
- Delete a StatefulSet
- DeleteOptions — DeleteOptions may be provided when deleting an API object.
- Deploy an App — Run and manage your application in Kubernetes.
- Deploy and Access the Kubernetes Dashboard — Deploy the web UI (Kubernetes Dashboard) and access it.
- Deployment — Deployment enables declarative updates for Pods and ReplicaSets.
- DeploymentReplicaSetTerminatingReplicas — Deployment Replica Set Terminating Replicas is a feature gate that enables the deletion of terminating replicas in deployments.
- Deployments — A Deployment manages a set of Pods to run an application workload, usually one that doesn't maintain state.
- Deprecated API Migration Guide
- DetectCacheInconsistency — Detects cache inconsistency in Kubernetes.
- Determine the Reason for Pod Failure
- Developing and debugging services locally using telepresence
- Developing Cloud Controller Manager
- Device Plugins — Device plugins let you configure your cluster with support for devices or resources that require vendor-specific setup, such as GPUs, NICs, FPGAs, or non-volatile main memory.
- DeviceClass — DeviceClass is a vendor- or admin-provided resource that contains device configuration and selectors. It can be referenced in the device requests of a claim to apply these presets. Cluster scoped.
- DevicePluginCDIDevices — Enables the use of Device Plugin's CIDevice feature.
- DevicePlugins — DevicePlugins is a feature gate that enables device plugin functionality.
- DeviceTaintRule — DeviceTaintRule adds one taint to all devices which match the selector. This has the same effect as if the taint was specified directly in the ResourceSlice by the DRA driver.
- DisableAcceleratorUsageMetrics — Disables accelerator usage metrics.
- DisableAllocatorDualWrite — A feature gate that disables allocator dual write for Kubernetes components.
- DisableCloudProviders — Disables cloud providers for Kubernetes.
- DisableCPUQuotaWithExclusiveCPUs — A feature gate that disables CPU quota with exclusive CPUs.
- DisableKubeletCloudCredentialProviders — Disables cloud credential providers in Kubelet.
- DisableNodeKubeProxyVersion — DisableNodeKubeProxyVersion is a feature gate that disables the version check for kube-proxy on nodes.
- Discovery — Discovery is a feature in Kubernetes that enables pods and services to find each other within a cluster.
- Disruptions
- Distribute Credentials Securely Using Secrets
- DNS for Services and Pods — Your workload can discover Services within your cluster using DNS; this page explains how that works.
- Docs smoke test page
- Documentation — Documentation is available for Kubernetes.
- Downward API — There are two ways to expose Pod and container fields to a running container: environment variables, and as files that are populated by a special volume type. Together, these two ways of exposing Pod and container fields are called the downward API.
- DownwardAPIHugePages — Provides access to huge pages through Downward API in Kubernetes.
- DRAAdminAccess
- DRAConsumableCapacity — DRAConsumableCapacity is a feature gate that allows for adjustable resource consumption in DRA.
- DRAControlPlaneController — DRAControlPlaneController is a feature gate that enables or disables the DRA Control Plane Controller.
- DRADeviceBindingConditions — DRADeviceBindingConditions is a feature gate in Kubernetes.
- DRADeviceTaintRules — DRADeviceTaintRules is a feature gate that allows device taint rules for DRAs.
- DRADeviceTaints — A feature gate that enables Device Taints for DRAs.
- DRAExtendedResource — DRAExtendedResource is a feature gate that controls whether extended resources are allowed for Distributed Resource Allocation (DRA).
- DRAListTypeAttributes
- DRANodeAllocatableResources
- DRAPartitionableDevices — A feature gate that allows partitioning devices using DRAs.
- DRAPrioritizedList — DRAPrioritizedList is a feature gate that enables prioritized deletion of resources.
- DRAResourceClaimDeviceStatus — DRAResourceClaimDeviceStatus is a feature gate that enables device status reporting for DRA (Device Resource Allocation) resource claims.
- DRAResourceClaimGranularStatusAuthorization — DRAResourceClaimGranularStatusAuthorization is a feature gate that enables granular status authorization for DRA resource claims.
- DRAResourcePoolStatus — DRAResourcePoolStatus is a feature gate that enables DRA resource pool status reporting.
- DRASchedulerFilterTimeout — DRASchedulerFilterTimeout is a feature gate that enables the use of a timeout for DRA (Dynamic Resource Allocation) scheduler filters.
- DRAWorkloadResourceClaims — DRAWorkloadResourceClaims is a feature gate that enables DRA workload resource claims.
- DryRun — DryRun is a feature gate that enables dry-run mode for Kubernetes commands.
- Dual-stack support with kubeadm
- Dynamic Admission Control
- Dynamic Resource Allocation
- Dynamic Volume Provisioning
- DynamicAuditing — DynamicAuditing is a feature gate that enables dynamic auditing for Kubernetes clusters.
- DynamicKubeletConfig — DynamicKubeletConfig enables dynamic configuration of Kubelet.
- DynamicProvisioningScheduling — A feature gate that enables dynamic provisioning and scheduling.
- DynamicResourceAllocation — DynamicResourceAllocation is a feature gate that enables dynamic resource allocation.
- DynamicVolumeProvisioning — A feature gate that enables dynamic volume provisioning for Kubernetes components.
- EfficientWatchResumption — EfficientWatchResumption optimizes watch resumption in Kubernetes.
- ElasticIndexedJob — ElasticIndexedJob is a feature gate that enables elastic indexing for jobs.
- Enable Or Disable A Kubernetes API
- Enable Or Disable Feature Gates
- EnableAggregatedDiscoveryTimeout — EnableAggregatedDiscoveryTimeout is a feature gate that allows configuring the aggregated discovery timeout in Kubernetes.
- EnableEquivalenceClassCache — Enable Equivalence Class Cache is a feature gate that enables caching of equivalence classes in the scheduler.
- Encodings — The process of converting data into a format that can be understood by different systems or applications.
- Encrypting Confidential Data at Rest
- Endpoints — Endpoints is a collection of endpoints that implement the actual service. Example: Name: "mysvc", Subsets: [ { Addresses: [{"ip": "10.10.1.1"}, {"ip": "10.10.2.2"}], Ports: [{"name": "a", "port": 8675}, {"name": "b", "port": 309}] }, { Addresses: [{"ip": "10.10.3.3"}], Ports: [{"name": "a", "port": 93}, {"name": "b", "port": 76}] }, ] Endpoints is a legacy API and does not contain information about all Service features. Use discoveryv1.EndpointSlice for complete information about Service endpoints. Deprecated: This API is deprecated in v1.33+. Use discoveryv1.EndpointSlice.
- EndpointSlice — EndpointSlice represents a set of service endpoints. Most EndpointSlices are created by the EndpointSlice controller to represent the Pods selected by Service objects. For a given service there may be multiple EndpointSlice objects which must be joined to produce the full set of endpoints; you can find all of the slices for a given service by listing EndpointSlices in the service's namespace whose `kubernetes.io/service-name` label contains the service's name.
- EndpointSlice — EndpointSlice is a feature gate that enables or disables the Endpoint Slice functionality.
- EndpointSliceNodeName — Configures the node name used for EndpointSlices.
- EndpointSliceProxying — A feature gate for enabling endpoint slice proxying.
- EndpointSlices — The EndpointSlice API is the mechanism that Kubernetes uses to let your Service scale to handle large numbers of backends, and allows the cluster to update its list of healthy backends efficiently.
- EndpointSliceTerminatingCondition — EndpointSliceTerminatingCondition is a feature gate that enables support for terminating conditions in EndpointSlices.
- Enforce Pod Security Standards by Configuring the Built-in Admission Controller
- Enforce Pod Security Standards with Namespace Labels
- Enforcing Pod Security Standards
- EnvFiles — EnvFiles allows you to load environment variables from files.
- Ephemeral Containers
- Ephemeral Volumes
- EphemeralContainers — Ephemeral Containers are a feature in Kubernetes that allows for the creation of temporary, short-lived containers.
- EvenPodsSpread — EvenPodsSpread is a feature gate that enables or disables even pod spread.
- Event — Event is a report of an event somewhere in the cluster. Events have a limited retention time and triggers and messages may evolve with time. Event consumers should not rely on the timing of an event with a given Reason reflecting a consistent underlying trigger, or the continued existence of events with that Reason. Events should be treated as informative, best-effort, supplemental data.
- Event — Event is a report of an event somewhere in the cluster. It generally denotes some state change in the system. Events have a limited retention time and triggers and messages may evolve with time. Event consumers should not rely on the timing of an event with a given Reason reflecting a consistent underlying trigger, or the continued existence of events with that Reason. Events should be treated as informative, best-effort, supplemental data.
- Event Rate Limit Configuration (v1alpha1)
- EventedPLEG — EventedPLEG is a feature gate that enables event-driven pod lifecycle events in Kubernetes.
- Events — Events are a way for Kubernetes to report on the status of resources.
- EventSource — EventSource contains information for an event.
- Eviction — Eviction evicts a pod from its node subject to certain policies and safety constraints. This is a subresource of Pod. A request to cause such an eviction is created by POSTing to .../pods/<pod name>/evictions.
- Example: Deploying Cassandra with a StatefulSet
- Example: Deploying PHP Guestbook application with Redis
- Example: Deploying WordPress and MySQL with Persistent Volumes
- ExecProbeTimeout — A feature gate that controls the timeout for exec probes.
- ExpandCSIVolumes — A feature gate that enables expanding CSI volumes.
- ExpandedDNSConfig — ExpandedDNSConfig is a feature gate that allows for more flexible DNS configuration in Kubernetes.
- ExpandInUsePersistentVolumes — ExpandInUsePersistentVolumes is a feature gate that enables or disables the expansion of in-use persistent volumes.
- ExpandPersistentVolumes — ExpandPersistentVolumes is a feature gate that enables expansion of persistent volumes.
- ExperimentalCriticalPodAnnotation — ExperimentalCriticalPodAnnotation is a feature gate that enables the annotation of critical pods for priority handling.
- ExperimentalHostUserNamespaceDefaulting — Experimental Host User Namespace Defaulting allows for more flexible namespace management.
- Explore Termination Behavior for Pods And Their Endpoints
- Explore Validating and Mutating Admission Policies — Use declarative admission policies to validate or mutate resources at admission time using Common Expression Language (CEL).
- Explore Your App — Explore Your App to gain insights into its performance, resource utilization, and behavior within the Kubernetes cluster.
- Expose Pod Information to Containers Through Environment Variables
- Expose Pod Information to Containers Through Files
- Expose Your App Publicly — Make your application accessible from outside the cluster.
- Exposing an External IP Address to Access an Application in a Cluster
- Extend kubectl with plugins — Extend kubectl by creating and installing kubectl plugins.
- Extend Kubernetes — Understand advanced ways to adapt your Kubernetes cluster to the needs of your work environment.
- Extend Service IP Ranges
- Extend the Kubernetes API with CustomResourceDefinitions
- Extending Kubernetes — Different ways to change the behavior of your Kubernetes cluster.
- Extending the Kubernetes API
- ExtendWebSocketsToKubelet — ExtendWebSocketsToKubelet is a feature gate that enables or disables the extension of websockets to kubelet.
- External APIs — External APIs are external interfaces that allow users to interact with the Kubernetes cluster from outside the cluster.
- ExternalPolicyForExternalIP — A feature gate that enables external policy for external IP.
- ExternalServiceAccountTokenSigner — Uses an external service account token signer.
- Feature Gates
- Feature Gates (removed)
- Field Selectors
- FieldSelectorAttributes — FieldSelectorAttributes indicates a field limited access. Webhook authors are encouraged to * ensure rawSelector and requirements are not both set * consider the requirements field if set * not try to parse or consider the rawSelector field if set. This is to avoid another CVE-2022-2880 (i.e. getting different systems to agree on how exactly to parse a query is not something we want), see https://www.oxeye.io/resources/golang-parameter-smuggling-attack for more details. For the *SubjectAccessReview endpoints of the kube-apiserver: * If rawSelector is empty and requirements are empty, the request is not limited. * If rawSelector is present and requirements are empty, the rawSelector will be parsed and limited if the parsing succeeds. * If rawSelector is empty and requirements are present, the requirements should be honored * If rawSelector is present and requirements are present, the request is invalid.
- FieldSelectorRequirement — FieldSelectorRequirement is a selector that contains values, a key, and an operator that relates the key and values.
- FieldsV1 — FieldsV1 stores a set of fields in a data structure like a Trie, in JSON format. Each key is either a '.' representing the field itself, and will always map to an empty set, or a string representing a sub-field or item. The string will follow one of these four formats: 'f:<name>', where <name> is the name of a field in a struct, or key in a map 'v:<value>', where <value> is the exact json formatted value of a list item 'i:<index>', where <index> is position of a item in a list 'k:<keys>', where <keys> is a map of a list item's key fields to their unique values If a key maps to an empty Fields value, the field that key represents is part of the set. The exact format is defined in sigs.k8s.io/structured-merge-diff
- Finalizers
- Find Out What Container Runtime is Used on a Node
- Fine Parallel Processing Using a Work Queue
- fish auto-completion — Optional configuration to enable fish shell auto-completion.
- Flow control
- Flowcontrol — Flowcontrol is an internal component of Kubernetes that manages API requests.
- FlowSchema — FlowSchema defines the schema of a group of flows. Note that a flow is made up of a set of inbound API requests with similar attributes and is identified by a pair of strings: the name of the FlowSchema and a "flow distinguisher".
- Force Delete StatefulSet Pods
- Gang Scheduling
- GangScheduling — GangScheduling is a feature gate that enables gang scheduling for pods.
- Garbage Collection
- Gateway API — Gateway API is a family of API kinds that provide dynamic infrastructure provisioning and advanced traffic routing.
- GCERegionalPersistentDisk — GCERegionalPersistentDisk is a feature gate that enables the use of regional persistent disks with GCE.
- Generate Certificates Manually
- GenericEphemeralVolume — Generic Ephemeral Volume is a feature gate that enables the use of generic ephemeral volumes in Kubernetes.
- GenericWorkload — GenericWorkload is a feature gate that enables generic workload support.
- Get a Shell to a Running Container
- Getting started
- GitRepoVolumeDriver
- Good practices for Dynamic Resource Allocation as a Cluster Admin
- Good practices for Kubernetes Secrets — Principles and practices for good Secret management for cluster administrators and application developers.
- GracefulNodeShutdown — GracefulNodeShutdown is a feature gate that allows for graceful shutdown of nodes.
- GracefulNodeShutdownBasedOnPodPriority — GracefulNodeShutdownBasedOnPodPriority is a feature gate that enables nodes to shut down based on pod priority.
- GroupResource — GroupResource specifies a Group and a Resource, but does not force a version. This is useful for identifying concepts during lookup stages without having partially valid types
- GroupVersionForDiscovery — GroupVersion contains the "group/version" and "version" string of a version. It is made a struct to keep extensibility.
- GRPCContainerProbe — GRPCContainerProbe is a feature gate that enables gRPC container probes.
- Guaranteed Scheduling For Critical Add-On Pods
- Guide for Running Windows Containers in Kubernetes
- Handling retriable and non-retriable pod failures with Pod failure policy
- Harden Dynamic Resource Allocation in Your Cluster
- Hardening Guide - Authentication Mechanisms — Information on authentication options in Kubernetes and their security properties.
- Hardening Guide - Dynamic Resource Allocation — Information about hardening Dynamic Resource Allocation (DRA) authorization and access patterns.
- Hardening Guide - Scheduler Configuration — Information about how to make the Kubernetes scheduler more secure.
- Hello Minikube
- HonorPVReclaimPolicy — A feature gate that enables honoring of PV reclaim policy.
- Horizontal Manual Scaling for a Deployment
- Horizontal Pod Autoscaling
- HorizontalPodAutoscaler — HorizontalPodAutoscaler is the configuration for a horizontal pod autoscaler, which automatically manages the replica count of any resource implementing the scale subresource based on the metrics specified.
- HorizontalPodAutoscaler Walkthrough
- HostnameOverride — HostnameOverride is a feature gate that allows overriding the hostname of a node.
- HPAConfigurableTolerance — Enables configurable tolerance for Horizontal Pod Autoscalers.
- HPAContainerMetrics — HPAContainerMetrics is a feature gate that enables Horizontal Pod Autoscaler (HPA) to use container metrics.
- HPAScaleToZero — HPAScaleToZero is a feature gate that enables or disables the ability to scale Horizontal Pod Autoscalers (HPAs) to zero replicas.
- HugepageAwareEviction — HugepageAwareEviction is a feature gate that enables eviction of huge pages.
- HugePages — Enables Huge Pages feature.
- HugePageStorageMediumSize — A feature gate that enables huge page storage with medium size.
- HyperVContainer — Supports Hyper-V containers in Kubernetes.
- IdentifyPodOS — A feature gate that allows you to identify the operating system of a pod.
- Image Policy API (v1alpha1)
- ImageMaximumGCAge — ImageMaximumGCAge is a feature gate that sets the maximum age of images in the cluster.
- Images
- ImageVolume — ImageVolume is a feature gate that enables the use of images as volumes.
- ImageVolumeWithDigest — ImageVolumeWithDigest is a feature gate that enables the use of image volumes with digests.
- ImmutableEphemeralVolumes
- Imperative Management of Kubernetes Objects Using Configuration Files
- Implementation details
- Indexed Job for Parallel Processing with Static Work Assignment
- IndexedJob — IndexedJob is a feature gate that enables indexing for jobs.
- InformerResourceVersion — A feature gate for enabling informer resource versioning.
- Ingress — Make your HTTP (or HTTPS) network service available using a protocol-aware configuration mechanism, that understands web concepts like URIs, hostnames, paths, and more. The Ingress concept lets you map traffic to different backends based on rules you define via the Kubernetes API.
- Ingress — Ingress is a collection of rules that allow inbound connections to reach the endpoints defined by a backend. An Ingress can be configured to give services externally-reachable urls, load balance traffic, terminate SSL, offer name based virtual hosting etc.
- Ingress Controllers — In order for an [Ingress](/docs/concepts/services-networking/ingress/) to work in your cluster, there must be an _ingress controller_ running. You need to select at least one ingress controller and make sure it is set up in your cluster. This page lists common ingress controllers that you can deploy.
- IngressClass — IngressClass represents the class of the Ingress, referenced by the Ingress Spec. The `ingressclass.kubernetes.io/is-default-class` annotation can be used to indicate that an IngressClass should be considered default. When a single IngressClass resource has this annotation set to true, new Ingress resources without a class specified will be assigned this default class.
- IngressClassNamespacedParams — IngressClassNamespacedParams is a feature gate that controls whether Ingress Class parameters are namespaced.
- Init Containers
- Initializers — A feature gate for enabling initializers.
- Inject Data Into Applications — Specify configuration and other data for the Pods that run your workload.
- InOrderInformers — InOrderInformers is a feature gate that enables in-order informer processing.
- InPlacePodLevelResourcesVerticalScaling — Enables in-place scaling of pod-level resources.
- InPlacePodVerticalScaling — Enables in-place pod vertical scaling, allowing for automatic resizing of pods without restarting them.
- InPlacePodVerticalScalingAllocatedStatus — In-Place Pod Vertical Scaling Allocated Status is a feature gate that enables the display of allocated resources for pods.
- InPlacePodVerticalScalingExclusiveCPUs — Enables In-Place Pod Vertical Scaling for exclusive CPUs.
- InPlacePodVerticalScalingExclusiveMemory — InPlacePodVerticalScalingExclusiveMemory is a feature gate that enables in-place pod vertical scaling with exclusive memory.
- Install a Network Policy Provider — Install a Network Policy Provider to manage network traffic within your cluster.
- Install and Set Up kubectl on Linux
- Install and Set Up kubectl on macOS
- Install and Set Up kubectl on Windows
- Install Drivers and Allocate Devices with DRA
- Install Tools — Set up Kubernetes tools on your computer.
- Installing Addons
- Installing kubeadm
- Installing Kubernetes with deployment tools
- Instrumentation — A collection of instrumentation-related resources and guides.
- InTreePluginAWSUnregister — InTreePluginAWSUnregister is a feature gate that allows you to unregister in-tree plugins for AWS.
- InTreePluginAzureDiskUnregister — InTreePluginAzureDiskUnregister is a feature gate that enables the use of in-tree Azure disk unregister functionality in Kubernetes.
- InTreePluginAzureFileUnregister — A feature gate for enabling in-tree plugin Azure File unregister.
- InTreePluginGCEUnregister — Unregisters in-tree GCE plugins.
- InTreePluginOpenStackUnregister — In-Tree Plugin OpenStack Unregister is a feature gate in Kubernetes that allows for the unregistration of OpenStack plugins.
- InTreePluginPortworxUnregister — In-Tree Plugin Portworx Unregister is a feature gate in Kubernetes that allows for the unregistration of Portworx plugins.
- InTreePluginRBDUnregister — InTreePluginRBDUnregister is a feature gate that enables or disables the ability to unregister RBD plugins from within the cluster.
- InTreePluginvSphereUnregister — A feature gate to unregister In-Tree vSphere plugins.
- Introduction to kubectl
- IP Masquerade Agent User Guide
- IPAddress — IPAddress represents a single IP of a single IP Family. The object is designed to be used by APIs that operate on IP addresses. The object is used by the Service core API for allocation of IP addresses. An IP address can be represented in different formats, to guarantee the uniqueness of the IP, the name of the object is the IP address in canonical format, four decimal digits separated by dots suppressing leading zeros for IPv4 and the representation defined by RFC 5952 for IPv6. Valid: 192.168.1.5 or 2001:db8::1 or 2001:db8:aaaa:bbbb:cccc:dddd:eeee:1 Invalid: 10.01.2.3 or 2001:db8:0:0:0::1
- IPTablesOwnershipCleanup — IPTablesOwnershipCleanup is a feature gate that enables or disables the cleanup of IP tables ownership.
- IPv4/IPv6 dual-stack — Kubernetes lets you configure single-stack IPv4 networking, single-stack IPv6 networking, or dual stack networking with both network families active. This page explains how.
- IPv6DualStack — IPv6DualStack is a feature gate that enables IPv6 and IPv4 dual stack support in pods.
- Issue a Certificate for a Kubernetes API Client Using a CertificateSigningRequest
- Job — Job represents the configuration of a single job.
- Job with Pod-to-Pod Communication
- JobBackoffLimitPerIndex — JobBackoffLimitPerIndex is a feature gate that allows job backoff limits to be set per index, enabling more granular control over job retries.
- JobManagedBy — A feature gate that indicates whether a job is managed by the cluster.
- JobMutableNodeSchedulingDirectives — JobMutableNodeSchedulingDirectives is a feature gate that allows mutable node scheduling directives for jobs.
- JobPodFailurePolicy — JobPodFailurePolicy is a feature gate that controls the behavior of Job pods when they fail.
- JobPodReplacementPolicy — Job Pod Replacement Policy allows for more control over pod replacement in jobs.
- JobReadyPods — JobReadyPods is a feature gate that allows pods to be considered ready for use by jobs even if they have not yet completed their startup process.
- Jobs — Jobs represent one-off tasks that run to completion and then stop.
- JobSuccessPolicy — JobSuccessPolicy is a feature gate that enables or disables the ability to specify a success policy for jobs.
- JobTrackingWithFinalizers — JobTrackingWithFinalizers is a feature gate that allows jobs to be tracked and finalized.
- JSONPath Support
- KMSv1 — A feature gate for enabling KMS v1.
- KMSv2 — KMSv2 is a feature gate that enables the use of AWS Key Management Service version 2.
- KMSv2KDF — A feature gate for enabling or disabling the use of KMS v2 Key Data Format.
- kube-apiserver
- kube-apiserver Admission (v1)
- kube-apiserver Audit Configuration (v1)
- kube-apiserver Configuration (v1)
- kube-apiserver Configuration (v1alpha1)
- kube-apiserver Configuration (v1beta1)
- kube-controller-manager
- kube-controller-manager Configuration (v1alpha1)
- kube-proxy
- kube-proxy Configuration (v1alpha1)
- kube-scheduler
- kube-scheduler Configuration (v1)
- kubeadm
- Kubeadm
- kubeadm alpha
- kubeadm certs
- kubeadm config
- kubeadm Configuration (v1beta3)
- kubeadm Configuration (v1beta4)
- Kubeadm Generated — Kubeadm Generated refers to the automatically generated configuration files.
- kubeadm init
- kubeadm init phase
- kubeadm join
- kubeadm join phase
- kubeadm kubeconfig — kubeadm kubeconfig generates a Kubernetes configuration file.
- kubeadm reset
- kubeadm reset phase
- kubeadm token
- kubeadm upgrade
- kubeadm upgrade phases
- kubeadm version — kubeadm version displays the kubeadm version and Git commit hash.
- kubeadm_certs_certificate-key
- kubeadm_certs_check-expiration
- kubeadm_certs_generate-csr
- kubeadm_certs_renew
- kubeadm_certs_renew_admin.conf
- kubeadm_certs_renew_all
- kubeadm_certs_renew_apiserver
- kubeadm_certs_renew_apiserver-etcd-client
- kubeadm_certs_renew_apiserver-kubelet-client
- kubeadm_certs_renew_controller-manager.conf
- kubeadm_certs_renew_etcd-healthcheck-client
- kubeadm_certs_renew_etcd-peer
- kubeadm_certs_renew_etcd-server
- kubeadm_certs_renew_front-proxy-client
- kubeadm_certs_renew_scheduler.conf
- kubeadm_certs_renew_super-admin.conf
- kubeadm_config_images
- kubeadm_config_images_list
- kubeadm_config_images_pull
- kubeadm_config_migrate
- kubeadm_config_print
- kubeadm_config_print_init-defaults
- kubeadm_config_print_join-defaults
- kubeadm_config_print_reset-defaults
- kubeadm_config_print_upgrade-defaults
- kubeadm_config_validate
- kubeadm_init_phase
- kubeadm_init_phase_addon
- kubeadm_init_phase_addon_all
- kubeadm_init_phase_addon_coredns
- kubeadm_init_phase_addon_kube-proxy
- kubeadm_init_phase_bootstrap-token
- kubeadm_init_phase_certs
- kubeadm_init_phase_certs_all
- kubeadm_init_phase_certs_apiserver
- kubeadm_init_phase_certs_apiserver-etcd-client
- kubeadm_init_phase_certs_apiserver-kubelet-client
- kubeadm_init_phase_certs_ca
- kubeadm_init_phase_certs_etcd-ca
- kubeadm_init_phase_certs_etcd-healthcheck-client
- kubeadm_init_phase_certs_etcd-peer
- kubeadm_init_phase_certs_etcd-server
- kubeadm_init_phase_certs_front-proxy-ca
- kubeadm_init_phase_certs_front-proxy-client
- kubeadm_init_phase_certs_sa
- kubeadm_init_phase_control-plane
- kubeadm_init_phase_control-plane_all
- kubeadm_init_phase_control-plane_apiserver
- kubeadm_init_phase_control-plane_controller-manager
- kubeadm_init_phase_control-plane_scheduler
- kubeadm_init_phase_etcd
- kubeadm_init_phase_etcd_local
- kubeadm_init_phase_kubeconfig
- kubeadm_init_phase_kubeconfig_admin
- kubeadm_init_phase_kubeconfig_all
- kubeadm_init_phase_kubeconfig_controller-manager
- kubeadm_init_phase_kubeconfig_kubelet
- kubeadm_init_phase_kubeconfig_scheduler
- kubeadm_init_phase_kubeconfig_super-admin
- kubeadm_init_phase_kubelet-finalize
- kubeadm_init_phase_kubelet-finalize_all
- kubeadm_init_phase_kubelet-finalize_enable-client-cert-rotation
- kubeadm_init_phase_kubelet-start
- kubeadm_init_phase_mark-control-plane
- kubeadm_init_phase_preflight
- kubeadm_init_phase_show-join-command
- kubeadm_init_phase_upload-certs
- kubeadm_init_phase_upload-config
- kubeadm_init_phase_upload-config_all
- kubeadm_init_phase_upload-config_kubeadm
- kubeadm_init_phase_upload-config_kubelet
- kubeadm_init_phase_wait-control-plane
- kubeadm_join_phase
- kubeadm_join_phase_control-plane-join
- kubeadm_join_phase_control-plane-join_all
- kubeadm_join_phase_control-plane-join_mark-control-plane
- kubeadm_join_phase_control-plane-prepare
- kubeadm_join_phase_control-plane-prepare_all
- kubeadm_join_phase_control-plane-prepare_certs
- kubeadm_join_phase_control-plane-prepare_control-plane
- kubeadm_join_phase_control-plane-prepare_download-certs
- kubeadm_join_phase_control-plane-prepare_kubeconfig
- kubeadm_join_phase_etcd-join
- kubeadm_join_phase_kubelet-start
- kubeadm_join_phase_kubelet-wait-bootstrap
- kubeadm_join_phase_preflight
- kubeadm_join_phase_wait-control-plane
- kubeadm_kubeconfig_user
- kubeadm_reset_phase
- kubeadm_reset_phase_cleanup-node
- kubeadm_reset_phase_preflight
- kubeadm_reset_phase_remove-etcd-member
- kubeadm_token_create
- kubeadm_token_delete
- kubeadm_token_generate
- kubeadm_token_list
- kubeadm_upgrade_apply
- kubeadm_upgrade_apply_phase
- kubeadm_upgrade_apply_phase_addon
- kubeadm_upgrade_apply_phase_addon_all
- kubeadm_upgrade_apply_phase_addon_coredns
- kubeadm_upgrade_apply_phase_addon_kube-proxy
- kubeadm_upgrade_apply_phase_bootstrap-token
- kubeadm_upgrade_apply_phase_control-plane
- kubeadm_upgrade_apply_phase_kubelet-config
- kubeadm_upgrade_apply_phase_post-upgrade
- kubeadm_upgrade_apply_phase_preflight
- kubeadm_upgrade_apply_phase_upload-config
- kubeadm_upgrade_apply_phase_upload-config_all
- kubeadm_upgrade_apply_phase_upload-config_kubeadm
- kubeadm_upgrade_apply_phase_upload-config_kubelet
- kubeadm_upgrade_diff
- kubeadm_upgrade_node
- kubeadm_upgrade_node_phase
- kubeadm_upgrade_node_phase_addon
- kubeadm_upgrade_node_phase_addon_all
- kubeadm_upgrade_node_phase_addon_coredns
- kubeadm_upgrade_node_phase_addon_kube-proxy
- kubeadm_upgrade_node_phase_control-plane
- kubeadm_upgrade_node_phase_kubelet-config
- kubeadm_upgrade_node_phase_post-upgrade
- kubeadm_upgrade_node_phase_preflight
- kubeadm_upgrade_plan
- kubeconfig (v1)
- kubectl
- kubectl — kubectl controls the Kubernetes cluster manager
- kubectl annotate — Update the annotations on a resource
- kubectl api-resources — Print the supported API resources on the server
- kubectl api-versions — Print the supported API versions on the server, in the form of "group/version"
- kubectl apply — Apply a configuration to a resource by file name or stdin
- kubectl apply edit-last-applied — Edit latest last-applied-configuration annotations of a resource/object
- kubectl apply set-last-applied — Set the last-applied-configuration annotation on a live object to match the contents of a file
- kubectl apply view-last-applied — View the latest last-applied-configuration annotations of a resource/object
- kubectl attach — Attach to a running container
- kubectl auth — Inspect authorization
- kubectl auth can-i — Check whether an action is allowed
- kubectl auth reconcile — Reconciles rules for RBAC role, role binding, cluster role, and cluster role binding objects
- kubectl auth whoami — Experimental: Check self subject attributes
- kubectl autoscale — Auto-scale a deployment, replica set, stateful set, or replication controller
- kubectl certificate — Modify certificate resources
- kubectl certificate approve — Approve a certificate signing request
- kubectl certificate deny — Deny a certificate signing request
- kubectl cluster-info — Display cluster information
- kubectl cluster-info dump — Dump relevant information for debugging and diagnosis
- kubectl Commands — kubectl Commands is a page that lists available kubectl commands.
- kubectl completion — Output shell completion code for the specified shell (bash, zsh, fish, or powershell)
- kubectl config — Modify kubeconfig files
- kubectl config current-context — Display the current-context
- kubectl config delete-cluster — Delete the specified cluster from the kubeconfig
- kubectl config delete-context — Delete the specified context from the kubeconfig
- kubectl config delete-user — Delete the specified user from the kubeconfig
- kubectl config get-clusters — Display clusters defined in the kubeconfig
- kubectl config get-contexts — Describe one or many contexts
- kubectl config get-users — Display users defined in the kubeconfig
- kubectl config rename-context — Rename a context from the kubeconfig file
- kubectl config set — Set an individual value in a kubeconfig file
- kubectl config set-cluster — Set a cluster entry in kubeconfig
- kubectl config set-context — Set a context entry in kubeconfig
- kubectl config set-credentials — Set a user entry in kubeconfig
- kubectl config unset — Unset an individual value in a kubeconfig file
- kubectl config use-context — Set the current-context in a kubeconfig file
- kubectl config view — Display merged kubeconfig settings or a specified kubeconfig file
- kubectl cordon — Mark node as unschedulable
- kubectl cp — Copy files and directories to and from containers
- kubectl create — Create a resource from a file or from stdin
- kubectl create clusterrole — Create a cluster role
- kubectl create clusterrolebinding — Create a cluster role binding for a particular cluster role
- kubectl create configmap — Create a config map from a local file, directory or literal value
- kubectl create cronjob — Create a cron job with the specified name
- kubectl create deployment — Create a deployment with the specified name
- kubectl create ingress — Create an ingress with the specified name
- kubectl create job — Create a job with the specified name
- kubectl create namespace — Create a namespace with the specified name
- kubectl create poddisruptionbudget — Create a pod disruption budget with the specified name
- kubectl create priorityclass — Create a priority class with the specified name
- kubectl create quota — Create a quota with the specified name
- kubectl create role — Create a role with single rule
- kubectl create rolebinding — Create a role binding for a particular role or cluster role
- kubectl create secret — Create a secret using a specified subcommand
- kubectl create secret docker-registry — Create a secret for use with a Docker registry
- kubectl create secret generic — Create a secret from a local file, directory, or literal value
- kubectl create secret tls — Create a TLS secret
- kubectl create service — Create a service using a specified subcommand
- kubectl create service clusterip — Create a ClusterIP service
- kubectl create service externalname — Create an ExternalName service
- kubectl create service loadbalancer — Create a LoadBalancer service
- kubectl create service nodeport — Create a NodePort service
- kubectl create serviceaccount — Create a service account with the specified name
- kubectl create token — Request a service account token
- kubectl debug — Create debugging sessions for troubleshooting workloads and nodes
- kubectl delete — Delete resources by file names, stdin, resources and names, or by resources and label selector
- kubectl describe — Show details of a specific resource or group of resources
- kubectl diff — Diff the live version against a would-be applied version
- kubectl drain — Drain node in preparation for maintenance
- kubectl edit — Edit a resource on the server
- kubectl events — List events
- kubectl exec — Execute a command in a container
- kubectl explain — Get documentation for a resource
- kubectl expose — Take a replication controller, service, deployment or pod and expose it as a new Kubernetes service
- kubectl for Docker Users
- kubectl get — Display one or many resources
- kubectl kuberc — Manage kuberc configuration files
- kubectl kuberc set — Set values in the kuberc configuration
- kubectl kuberc view — Display the current kuberc configuration
- kubectl kustomize — Build a kustomization target from a directory or URL
- kubectl label — Update the labels on a resource
- kubectl logs — Print the logs for a container in a pod
- kubectl options — Print the list of flags inherited by all commands
- kubectl patch — Update fields of a resource
- kubectl plugin — Provides utilities for interacting with plugins
- kubectl plugin list — List all visible plugin executables on a user's PATH
- kubectl port-forward — Forward one or more local ports to a pod
- kubectl proxy — Run a proxy to the Kubernetes API server
- kubectl Quick Reference
- kubectl reference — A reference document for kubectl commands and flags.
- kubectl replace — Replace a resource by file name or stdin
- kubectl rollout — Manage the rollout of a resource
- kubectl rollout history — View rollout history
- kubectl rollout pause — Mark the provided resource as paused
- kubectl rollout restart — Restart a resource
- kubectl rollout resume — Resume a paused resource
- kubectl rollout status — Show the status of the rollout
- kubectl rollout undo — Undo a previous rollout
- kubectl run — Run a particular image on the cluster
- kubectl scale — Set a new size for a deployment, replica set, or replication controller
- kubectl set — Set specific features on objects
- kubectl set env — Update environment variables on a pod template
- kubectl set image — Update the image of a pod template
- kubectl set resources — Update resource requests/limits on objects with pod templates
- kubectl set selector — Set the selector on a resource
- kubectl set serviceaccount — Update the service account of a resource
- kubectl set subject — Update the user, group, or service account in a role binding or cluster role binding
- kubectl taint — Update the taints on one or more nodes
- kubectl top — Display resource (CPU/memory) usage
- kubectl top node — Display resource (CPU/memory) usage of nodes
- kubectl top pod — Display resource (CPU/memory) usage of pods
- kubectl uncordon — Mark node as schedulable
- kubectl Usage Conventions
- Kubectl user preferences (kuberc)
- kubectl version — Print the client and server version information
- kubectl wait — Wait for a specific condition on one or many resources
- kubectl-convert overview — A kubectl plugin that allows you to convert manifests from one version of a Kubernetes API to a different version.
- kubelet
- Kubelet authentication/authorization
- Kubelet Checkpoint API
- Kubelet Configuration (v1)
- Kubelet Configuration (v1alpha1)
- Kubelet Configuration (v1beta1)
- Kubelet Configuration Directory Merging
- Kubelet CredentialProvider (v1)
- Kubelet Device Manager API Versions
- Kubelet Pod Info gRPC API
- Kubelet Sync Loop
- Kubelet Systemd Watchdog
- KubeletCgroupDriverFromCRI
- KubeletConfigFile — KubeletConfigFile is a feature gate that enables or disables the use of a configuration file for Kubelet.
- KubeletCrashLoopBackOffMax — KubeletCrashLoopBackOffMax is a feature gate that controls the maximum number of retries for Kubelet crash loops.
- KubeletCredentialProviders — KubeletCredentialProviders is a feature gate that enables Kubelet to use credential providers.
- KubeletEnsureSecretPulledImages — KubeletEnsureSecretPulledImages is a feature gate that enables the Kubelet to ensure secret-pulled images are used for pods.
- KubeletFineGrainedAuthz — A feature gate that enables fine-grained authorization for the Kubelet.
- KubeletInUserNamespace — Feature gate for enabling Kubelet in user namespace.
- KubeletPluginsWatcher — KubeletPluginsWatcher is a feature gate that enables the Kubelet to watch for plugin updates.
- KubeletPodResources — A feature gate for Kubelet pod resources.
- KubeletPodResourcesDynamicResources
- KubeletPodResourcesGet — KubeletPodResourcesGet is a feature gate that enables or disables the ability to get pod resources from the Kubelet.
- KubeletPodResourcesGetAllocatable — Determines how kubelet allocates resources for pods.
- KubeletPSI — KubeletPSI is a feature gate that enables Kubelet's Pod Security Indicator (PSI) functionality.
- KubeletSeparateDiskGC
- KubeletServiceAccountTokenForCredentialProviders — A feature gate that enables the use of Kubelet's service account token for credential providers.
- KubeletTracing — KubeletTracing is a feature gate that enables tracing for the Kubelet component.
- KubeProxyDrainingTerminatingNodes — A feature gate that enables Kube-proxy to drain and terminate nodes during upgrades.
- kuberc (v1alpha1)
- kuberc (v1beta1)
- Kubernetes API — A set of APIs that provide programmatic access to Kubernetes resources and functionality.
- Kubernetes API Aggregation Layer
- Kubernetes API Concepts
- Kubernetes API health endpoints
- Kubernetes API Server Bypass Risks — Security architecture information relating to the API server and other components
- Kubernetes Component SLI Metrics — High-level indicators for measuring the reliability and performance of Kubernetes components.
- Kubernetes Components — An overview of the key components that make up a Kubernetes cluster.
- Kubernetes Custom Metrics (v1beta2)
- Kubernetes Default ServiceCIDR Reconfiguration
- Kubernetes Deprecation Policy
- Kubernetes Documentation — Kubernetes is an open source container orchestration engine for automating deployment, scaling, and management of containerized applications. The open source project is hosted by the Cloud Native Computing Foundation.
- Kubernetes External Metrics (v1beta1)
- Kubernetes Issue Tracker
- Kubernetes Issues and Security — Kubernetes Issues and Security is a page that discusses security-related issues in Kubernetes.
- Kubernetes Metrics (v1beta1)
- Kubernetes Metrics Reference — Details of the metric data that Kubernetes components export.
- Kubernetes Object Management
- Kubernetes Scheduler
- Kubernetes Security and Disclosure Information
- Kubernetes Self-Healing
- Kubernetes z-pages — Provides runtime diagnostics for Kubernetes components, offering insights into component runtime status and configuration flags.
- KYAML Reference
- Labels and Selectors
- LabelSelector — A label selector is a label query over a set of resources. The result of matchLabels and matchExpressions are ANDed. An empty label selector matches all objects. A null label selector matches no objects.
- LabelSelectorAttributes — LabelSelectorAttributes indicates a label limited access. Webhook authors are encouraged to * ensure rawSelector and requirements are not both set * consider the requirements field if set * not try to parse or consider the rawSelector field if set. This is to avoid another CVE-2022-2880 (i.e. getting different systems to agree on how exactly to parse a query is not something we want), see https://www.oxeye.io/resources/golang-parameter-smuggling-attack for more details. For the *SubjectAccessReview endpoints of the kube-apiserver: * If rawSelector is empty and requirements are empty, the request is not limited. * If rawSelector is present and requirements are empty, the rawSelector will be parsed and limited if the parsing succeeds. * If rawSelector is empty and requirements are present, the requirements should be honored * If rawSelector is present and requirements are present, the request is invalid.
- LabelSelectorRequirement — A label selector requirement is a selector that contains values, a key, and an operator that relates the key and values.
- Learn Kubernetes Basics
- Learning environment
- Lease — Lease defines a lease concept.
- LeaseCandidate — LeaseCandidate defines a candidate for a Lease object. Candidates are created such that coordinated leader election will pick the best leader from the list of candidates.
- Leases
- LegacyNodeRoleBehavior — A feature gate for enabling legacy node role behavior.
- LegacyServiceAccountTokenCleanUp — LegacyServiceAccountTokenCleanUp is a feature gate that enables the cleanup of legacy service account tokens.
- LegacyServiceAccountTokenNoAutoGeneration
- LegacyServiceAccountTokenTracking — Tracks legacy service account tokens in Kubernetes.
- Limit Ranges
- Limit Storage Consumption
- LimitRange — LimitRange sets resource usage limits for each kind of resource in a Namespace.
- Linux kernel security constraints for Pods and containers — Overview of Linux kernel security modules and constraints that you can use to harden your Pods and containers.
- Linux Kernel Version Requirements
- Linux Node Swap Behaviors
- List All Container Images Running in a Cluster
- ListFromCacheSnapshot — ListFromCacheSnapshot is a feature gate that enables listing resources from cache snapshots.
- ListMeta — ListMeta describes metadata that synthetic resources must have, including lists and various status objects. A resource may have only one of {ObjectMeta, ListMeta}.
- Liveness, Readiness, and Startup Probes
- LoadBalancerIPMode — Configures the IP mode for load balancers.
- Local ephemeral storage
- Local Files And Paths Used By The Kubelet
- LocalObjectReference — LocalObjectReference contains enough information to let you locate the referenced object inside the same namespace.
- LocalStorageCapacityIsolation — Local Storage Capacity Isolation is a feature gate that allows for fine-grained control over the capacity of local storage volumes.
- LocalStorageCapacityIsolationFSQuotaMonitoring — LocalStorageCapacityIsolationFSQuotaMonitoring is a feature gate that enables filesystem quota monitoring for local storage.
- LocalSubjectAccessReview — LocalSubjectAccessReview checks whether or not a user or group can perform an action in a given namespace. Having a namespace scoped resource makes it much easier to grant namespace scoped policy that includes permissions checking.
- LogarithmicScaleDown — A feature gate that enables logarithmic scale down of pods.
- Logging Architecture
- Logging in Kubernetes — Logging in Kubernetes involves collecting, storing, and analyzing log data from applications and system components.
- LoggingAlphaOptions — LoggingAlphaOptions is a feature gate that enables alpha logging options.
- LoggingBetaOptions — The LoggingBetaOptions feature gate enables or disables beta features for logging.
- Manage Cluster Daemons — Perform common tasks for managing a DaemonSet, such as performing a rolling update.
- Manage HugePages — Configure and manage huge pages as a schedulable resource in a cluster.
- Manage Kubernetes Objects — Declarative and imperative paradigms for interacting with the Kubernetes API.
- Manage Memory, CPU, and API Resources — Manage Memory, CPU, and API Resources to ensure optimal cluster performance and security.
- Manage TLS Certificates in a Cluster
- ManagedFieldsEntry — ManagedFieldsEntry is a workflow-id, a FieldSet and the group version of the resource that the fieldset applies to.
- Managing Kubernetes Objects Using Imperative Commands
- Managing Secrets — Managing confidential settings data using Secrets.
- Managing Secrets using Configuration File — Creating Secret objects using resource configuration file.
- Managing Secrets using kubectl — Creating Secret objects using kubectl command line.
- Managing Secrets using Kustomize — Creating Secret objects using kustomization.yaml file.
- Managing Service Accounts
- Managing Workloads
- Manifest-Based Admission Control
- ManifestBasedAdmissionControlConfig — A feature gate that enables Manifest-Based Admission Control.
- Manual Rotation of CA Certificates
- Mapping PodSecurityPolicies to Pod Security Standards
- MatchCondition — MatchCondition represents a condition which must by fulfilled for a request to be sent to a webhook.
- MatchLabelKeysInPodAffinity — A feature gate that enables matching label keys in pod affinity.
- MatchLabelKeysInPodTopologySpread — MatchLabelKeysInPodTopologySpread is a feature gate that enables matching label keys in pod topology spread.
- MatchLabelKeysInPodTopologySpreadSelectorMerge — Feature gate for enabling match label keys in pod topology spread selector merge.
- MatchResources — MatchResources decides whether to run the admission control policy on an object based on whether it meets the match criteria. The exclude rules take precedence over include rules (if a resource matches both, it is excluded)
- MaxUnavailableStatefulSet — MaxUnavailableStatefulSet sets the maximum number of unavailable replicas for StatefulSets.
- MemoryManager — MemoryManager is a feature gate that allows for memory management.
- MemoryQoS — MemoryQoS is a feature gate that allows for memory quality of service.
- Metrics for Kubernetes Object States — kube-state-metrics, an add-on agent to generate and expose cluster-level metrics.
- Metrics For Kubernetes System Components
- MicroTime — MicroTime is version of Time with microsecond level precision.
- Migrate from PodSecurityPolicy to the Built-In PodSecurity Admission Controller
- Migrate Kubernetes Objects Using Storage Version Migration
- Migrate Replicated Control Plane To Use Cloud Controller Manager
- Migrating from dockershim
- Migrating telemetry and security agents from dockershim
- MinDomainsInPodTopologySpread — MinDomainsInPodTopologySpread is a feature gate that enables pod topology spread constraints with minimum domains.
- MinimizeIPTablesRestore — MinimizeIPTablesRestore is a feature gate that minimizes the number of iptables rules restored during a cluster restart.
- Mixed Version Proxy
- MixedProtocolLBService — MixedProtocolLBService is a feature gate that enables or disables Mixed Protocol Load Balancer Service.
- Monitor Node Health
- Monitoring in Kubernetes — Monitoring kubernetes system components.
- Monitoring, Logging, and Debugging — Set up monitoring and logging to troubleshoot a cluster, or debug a containerized application.
- MountContainers — MountContainers is a feature gate that allows containers to mount volumes at runtime.
- MountPropagation — A feature gate for enabling mount propagation.
- Multi-tenancy
- MultiCIDRRangeAllocator — MultiCIDRRangeAllocator is a feature gate that enables the use of multiple CIDR ranges for pod allocation.
- MultiCIDRServiceAllocator — A feature gate that enables the use of multiple CIDRs for service allocation.
- MutableCSINodeAllocatableCount — Enable Mutable CSI Node Allocatable Count to allow Kubernetes to dynamically adjust the allocatable count of a node.
- MutablePodResourcesForSuspendedJobs — MutablePodResourcesForSuspendedJobs is a feature gate that allows modifying pod resources for suspended jobs.
- MutablePVNodeAffinity — MutablePVNodeAffinity is a feature gate that allows modifying the node affinity of persistent volumes.
- MutableSchedulingDirectivesForSuspendedJobs — A feature gate for mutable scheduling directives on suspended jobs.
- Mutating Admission Policy
- MutatingAdmissionPolicy — MutatingAdmissionPolicy describes the definition of an admission mutation policy that mutates the object coming into admission chain.
- MutatingAdmissionPolicy — Mutating Admission Policy is a feature gate that enables admission policies to mutate incoming requests.
- MutatingAdmissionPolicyBinding — MutatingAdmissionPolicyBinding binds the MutatingAdmissionPolicy with parametrized resources. MutatingAdmissionPolicyBinding and the optional parameter resource together define how cluster administrators configure policies for clusters. For a given admission request, each binding will cause its policy to be evaluated N times, where N is 1 for policies/bindings that don't use params, otherwise N is the number of parameters selected by the binding. Each evaluation is constrained by a [runtime cost budget](https://kubernetes.io/docs/reference/using-api/cel/#runtime-cost-budget). Adding/removing policies, bindings, or params can not affect whether a given (policy, binding, param) combination is within its own CEL budget.
- MutatingWebhookConfiguration — MutatingWebhookConfiguration describes the configuration of and admission webhook that accept or reject and may change the object.
- NamedRuleWithOperations — NamedRuleWithOperations is a tuple of Operations and Resources with ResourceNames.
- Namespace — Namespace provides a scope for Names. Use of multiple namespaces is optional.
- NamespaceDefaultLabelName — NamespaceDefaultLabelName is a feature gate for setting the default label name for namespaces in Kubernetes.
- Namespaces
- Namespaces Walkthrough
- Native Histogram Support for Kubernetes Metrics
- NativeHistograms — NativeHistograms is a feature gate that enables native histograms.
- Network Plugins
- Network Policies — If you want to control traffic flow at the IP address or port level (OSI layer 3 or 4), NetworkPolicies allow you to specify rules for traffic flow within your cluster, and also between Pods and the outside world. Your cluster must use a network plugin that supports NetworkPolicy enforcement.
- Networking — Learn how to configure networking for your cluster.
- Networking — Networking is a feature in Kubernetes that provides connectivity between pods and services within a cluster.
- Networking on Windows
- Networking Reference — A collection of networking-related resources and guides.
- NetworkPolicy — NetworkPolicy describes what network traffic is allowed for a set of Pods
- NetworkPolicyEndPort — NetworkPolicyEndPort is a feature gate that allows network policies to specify end ports.
- NetworkPolicyStatus — Enables Network Policy Status feature.
- NewVolumeManagerReconstruction
- NFTablesProxyMode — Enables the use of NFTables proxy mode.
- Node — Node is a worker node in Kubernetes. Each node will have a unique identifier in the cache (i.e. in etcd).
- Node — A Node is a worker machine in Kubernetes, where containers are run.
- Node Autoscaling — Automatically provision and consolidate the Nodes in your cluster to adapt to demand and optimize cost.
- Node Declared Features
- Node Labels Populated By The Kubelet
- Node metrics data — Mechanisms for accessing metrics at node, volume, pod and container level, as seen by the kubelet.
- Node Reference Information
- Node Shutdowns
- Node Status
- Node-pressure Eviction
- Node-specific Volume Limits
- NodeDeclaredFeatures — NodeDeclaredFeatures is a feature gate that enables node-declared features.
- NodeDisruptionExclusion — NodeDisruptionExclusion is a feature gate that prevents node disruptions during cluster upgrades.
- NodeInclusionPolicyInPodTopologySpread — NodeInclusionPolicyInPodTopologySpread is a feature gate that enables node inclusion policy in pod topology spread.
- NodeLease — Manages node leases to prevent node reuse.
- NodeLogQuery — Enables the ability to query node logs.
- NodeOutOfServiceVolumeDetach — NodeOutOfServiceVolumeDetach is a feature gate that enables volume detachment on node out-of-service events.
- Nodes
- NodeSelector — A node selector represents the union of the results of one or more label queries over a set of nodes; that is, it represents the OR of the selectors represented by the node selector terms.
- NodeSelectorTerm — A null or empty node selector term matches no objects. The requirements of them are ANDed. The TopologySelectorTerm type implements a subset of the NodeSelectorTerm.
- NodeSwap — Node Swap is a feature gate that enables the swapping of nodes in Kubernetes.
- NominatedNodeNameForExpectation — Feature gate that enables node selection for pod scheduling.
- NonPreemptingPriority — NonPreemptingPriority is a feature gate that allows pods to run with non-preemptible priority.
- NonResourceAttributes — NonResourceAttributes includes the authorization attributes available for non-resource requests to the Authorizer interface
- NonResourceRule — NonResourceRule holds information that describes a rule for the non-resource
- Object Names and IDs
- ObjectMeta — ObjectMeta is metadata that all persisted resources must have, which includes all objects users must create.
- ObjectReference — ObjectReference contains enough information to let you inspect or modify the referred object.
- Objects In Kubernetes — Kubernetes objects are persistent entities in the Kubernetes system. Kubernetes uses these entities to represent the state of your cluster. Learn about the Kubernetes object model and how to work with these objects.
- Observability — Understand how to gain end-to-end visibility of a Kubernetes cluster through the collection of metrics, logs, and traces.
- Official CVE Feed
- OpenAPIEnums — OpenAPI Enums is a feature gate that enables the use of OpenAPI enums in Kubernetes APIs.
- OpenAPIV3 — OpenAPIV3 is a feature gate that enables OpenAPI V3 support.
- Operating etcd clusters for Kubernetes
- Operator pattern
- OpportunisticBatching — OpportunisticBatching enables opportunistic batching in Kubernetes.
- Options for Highly Available Topology
- OrderedNamespaceDeletion — A feature gate that enables ordered namespace deletion.
- Organizing Cluster Access Using kubeconfig Files
- Other Tools
- Overprovision Node Capacity For A Cluster
- Overview — Kubernetes is a portable, extensible, open source platform for managing containerized workloads and services that facilitate both declarative configuration and automation. It has a large, rapidly growing ecosystem. Kubernetes services, support, and tools are widely available.
- OwnerReference — OwnerReference contains enough information to let you identify an owning object. An owning object must be in the same namespace as the dependent, or be cluster-scoped, so there is no namespace field.
- Owners and Dependents
- Parallel Processing using Expansions
- ParamKind — ParamKind is a tuple of Group Kind and Version.
- ParamRef — ParamRef describes how to locate the params to be used as input to expressions of rules applied by a policy binding.
- Patch — Patch is provided to give a concrete name and type to the Kubernetes PATCH request body.
- PDBUnhealthyPodEvictionPolicy — PDBUnhealthyPodEvictionPolicy is a feature gate that controls the eviction policy for pods in a Pod Disruption Budget (PDB).
- Perform a Rollback on a DaemonSet
- Perform a Rolling Update on a DaemonSet
- Performing a Rolling Update
- Persistent Volumes
- PersistentLocalVolumes — A feature gate that enables or disables persistent local volumes.
- PersistentVolume — PersistentVolume (PV) is a storage resource provisioned by an administrator. It is analogous to a node. More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes
- PersistentVolumeClaim — PersistentVolumeClaim is a user's request for and claim to a persistent volume
- PersistentVolumeClaimUnusedSinceTime — PersistentVolumeClaimUnusedSinceTime is a feature gate that controls whether the time when a Persistent Volume Claim (PVC) was last used is tracked.
- PersistentVolumeLastPhaseTransitionTime — PersistentVolumeLastPhaseTransitionTime is a feature gate that allows you to control the visibility of persistent volume phase transition times.
- PKI certificates and requirements
- Pod — Pod is a collection of containers that can run on a host. This resource is created by clients and scheduled onto hosts.
- Pod Conditions
- Pod Group Disruption and Priority
- Pod Hostname
- Pod Lifecycle
- Pod Overhead
- Pod Priority and Preemption
- Pod Quality of Service Classes
- Pod Scheduling Readiness
- Pod Security Admission — An overview of the Pod Security Admission Controller, which can enforce the Pod Security Standards.
- Pod Security Policies
- Pod Security Standards — A detailed look at the different policy levels defined in the Pod Security Standards.
- Pod Topology Spread Constraints
- PodAffinityNamespaceSelector — PodAffinityNamespaceSelector is a feature gate that allows selecting pods based on namespace.
- PodAndContainerStatsFromCRI — PodAndContainerStatsFromCRI is a feature gate that allows retrieving pod and container statistics from the Container Runtime Interface (CRI).
- PodCertificateRequest — PodCertificateRequest encodes a pod requesting a certificate from a given signer. Kubelets use this API to implement podCertificate projected volumes
- PodCertificateRequest — Manages certificate requests for pods.
- PodDeletionCost — PodDeletionCost is a feature gate that enables the use of pod deletion cost in Kubernetes.
- PodDisruptionBudget — PodDisruptionBudget is an object to define the max disruption that can be caused to a collection of pods
- PodDisruptionBudget — The PodDisruptionBudget feature gate enables or disables pod disruption budgets.
- PodDisruptionConditions — PodDisruptionConditions is a feature gate that enables the use of pod disruption conditions in Kubernetes.
- PodGroup — PodGroup represents a runtime instance of pods grouped together. PodGroups are created by workload controllers (Job, LWS, JobSet, etc...) from Workload.podGroupTemplates. PodGroup API enablement is toggled by the GenericWorkload feature gate.
- PodGroup API
- PodGroup Lifecycle
- PodGroup Scheduling
- PodGroup Scheduling Policies
- PodHasNetworkCondition — A feature gate that enables or disables the PodHasNetworkCondition field in Kubernetes.
- PodHostIPs — A feature gate for enabling or disabling PodHostIPs.
- PodIndexLabel — PodIndexLabel is a feature gate that allows you to specify an index label for pods.
- PodInfoAPI — Feature gate that enables the Pod Info API.
- PodLevelResourceManagers — PodLevelResourceManagers is a feature gate that enables pod-level resource managers.
- PodLevelResources — PodLevelResources is a feature gate that enables pod-level resources.
- PodLifecycleSleepAction — A feature gate that allows specifying the sleep action for pods during lifecycle events.
- PodLifecycleSleepActionAllowZero — PodLifecycleSleepActionAllowZero is a feature gate that allows the Pod Lifecycle Hook to sleep for zero seconds.
- PodLogsQuerySplitStreams — PodLogsQuerySplitStreams is a feature gate that enables splitting logs into multiple streams.
- PodObservedGenerationTracking — A feature gate for enabling Pod Observed Generation Tracking.
- PodOverhead — A feature gate that enables pod overhead calculation.
- PodPriority — PodPriority is a feature gate that allows pods to be prioritized in terms of scheduling.
- PodReadinessGates — PodReadinessGates is a feature gate that allows you to define readiness gates for pods.
- PodReadyToStartContainersCondition — A feature gate that enables the PodReadyToStartContainers condition.
- Pods
- PodSchedulingReadiness — PodSchedulingReadiness enables readiness checks for pod scheduling.
- PodSecurity — PodSecurity is a feature gate that enables pod security policies.
- PodShareProcessNamespace — A feature gate that enables sharing process namespace between pods.
- PodTemplate — PodTemplate describes a template for creating copies of a predefined pod.
- PodTopologyLabelsAdmission — PodTopologyLabelsAdmission is a feature gate that enables admission control for pod topology.
- Policies — Manage security and best-practices with policies.
- Policy — Policy is a Kubernetes API that provides features for managing and enforcing cluster-wide policies.
- PolicyRule — PolicyRule holds information that describes a policy rule, but does not contain information about who the rule applies to or which namespace the rule applies to.
- PortForwardWebsockets — Enables WebSocket support for port forwarding.
- Ports and Protocols
- PowerShell auto-completion — Some optional configuration for powershell auto-completion.
- Preconditions — Preconditions must be fulfilled before an operation (update, delete, etc.) is carried out.
- PreferNominatedNode — Prioritizes nominated nodes for pod scheduling.
- PreferSameTrafficDistribution — Prefer Same Traffic Distribution is a feature gate that controls whether to prefer same traffic distribution for pods.
- PreventStaticPodAPIReferences — A feature gate that prevents static pod API references.
- PriorityClass — PriorityClass defines mapping from a priority class name to the priority integer value. The value can be any valid integer.
- PriorityLevelConfiguration — PriorityLevelConfiguration represents the configuration of a priority level.
- ProbeTerminationGracePeriod — Sets the termination grace period for probes.
- Process ID Limits And Reservations
- ProcMountType — ProcMountType is a feature gate that controls the mount type of /proc.
- Production environment — Create a production-quality Kubernetes cluster
- Projected Volumes
- Protocols for Services
- Proxies in Kubernetes
- ProxyTerminatingEndpoints — ProxyTerminatingEndpoints is a feature gate that enables or disables the use of terminating endpoints in proxies.
- Pull an Image from a Private Registry
- PVCProtection — PVCProtection is a feature gate that enables protection for Persistent Volume Claims.
- QOSReserved — QOSReserved is a feature gate that allows you to reserve Quality of Service (QoS) resources for pods.
- Quantity — Quantity is a fixed-point representation of a number. It provides convenient marshaling/unmarshaling in JSON and YAML, in addition to String() and AsInt64() accessors. The serialization format is: ``` <quantity> ::= <signedNumber><suffix> (Note that <suffix> may be empty, from the "" case in <decimalSI>.) <digit> ::= 0 | 1 | ... | 9 <digits> ::= <digit> | <digit><digits> <number> ::= <digits> | <digits>.<digits> | <digits>. | .<digits> <sign> ::= "+" | "-" <signedNumber> ::= <number> | <sign><number> <suffix> ::= <binarySI> | <decimalExponent> | <decimalSI> <binarySI> ::= Ki | Mi | Gi | Ti | Pi | Ei (International System of units; See: http://physics.nist.gov/cuu/Units/binary.html) <decimalSI> ::= m | "" | k | M | G | T | P | E (Note that 1024 = 1Ki but 1000 = 1k; I didn't choose the capitalization.) <decimalExponent> ::= "e" <signedNumber> | "E" <signedNumber> ``` No matter which of the three exponent forms is used, no quantity may represent a number greater than 2^63-1 in magnitude, nor may it have more than 3 decimal places. Numbers larger or more precise will be capped or rounded up. (E.g.: 0.1m will rounded up to 1m.) This may be extended in the future if we require larger or smaller quantities. When a Quantity is parsed from a string, it will remember the type of suffix it had, and will use the same type again when it is serialized. Before serializing, Quantity will be put in "canonical form". This means that Exponent/suffix will be adjusted up or down (with a corresponding increase or decrease in Mantissa) such that: - No precision is lost - No fractional digits will be emitted - The exponent (or suffix) is as large as possible. The sign will be omitted unless the number is negative. Examples: - 1.5 will be serialized as "1500m" - 1.5Gi will be serialized as "1536Mi" Note that the quantity will NEVER be internally represented by a floating point number. That is the whole point of this exercise. Non-canonical values will still parse as long as they are well formed, but will be re-emitted in their canonical form. (So always use canonical form, or don't diff.) This format is intended to make it difficult to use these numbers without writing some sort of special handling code in the hopes that that will cause implementors to also use a fixed point implementation.
- Rbac — A mechanism for controlling access to Kubernetes resources based on user identity and role.
- README — The README file provides information about Kubeadm generated files.
- README
- ReadOnlyAPIDataVolumes — A feature gate that enables read-only access to API data volumes.
- ReadWriteOncePod — Enables ReadWriteOnce access for Pods.
- Recommended Labels
- Reconfiguring a kubeadm cluster
- RecoverVolumeExpansionFailure — RecoverVolumeExpansionFailure recovers from volume expansion failures.
- RecursiveReadOnlyMounts — Enables recursive read-only mounts for pods.
- ReduceDefaultCrashLoopBackOffDecay — ReduceDefaultCrashLoopBackOffDecay is a feature gate that enables or disables the reduction of default crash loop back-off decay.
- Reference
- RelaxedDNSSearchValidation — A feature gate that relaxes DNS search validation.
- RelaxedEnvironmentVariableValidation — RelaxedEnvironmentVariableValidation is a feature gate that relaxes environment variable validation.
- RelaxedServiceNameValidation — Allows service names to be more flexible and relaxed in their naming conventions.
- ReloadKubeletServerCertificateFile — Enables the ability to reload the Kubelet server certificate file without restarting the Kubelet.
- RemainingItemCount — Remaining Item Count is a feature in Kubernetes that allows for the tracking of remaining items in a list.
- RemoteRequestHeaderUID — Feature gate that enables the inclusion of UIDs in remote request headers.
- RemoveSelfLink — A feature gate that removes self-link.
- ReplicaSet — A ReplicaSet's purpose is to maintain a stable set of replica Pods running at any given time. Usually, you define a Deployment and let that Deployment manage ReplicaSets automatically.
- ReplicaSet — ReplicaSet ensures that a specified number of pod replicas are running at any given time.
- ReplicationController — Legacy API for managing workloads that can scale horizontally. Superseded by the Deployment and ReplicaSet APIs.
- ReplicationController — ReplicationController represents the configuration of a replication controller.
- RequestManagement — RequestManagement is a feature gate that enables request management for Kubernetes resources.
- Reserve Compute Resources for System Daemons
- ResilientWatchCacheInitialization — Enable Resilient Watch Cache Initialization to improve the performance of watch operations in Kubernetes.
- Resize CPU and Memory Resources assigned to Containers
- Resize CPU and Memory Resources assigned to Pods
- Resource — Resources are the units of compute, memory, and storage that pods require.
- Resource Bin Packing
- Resource Management for Pods and Containers
- Resource Management for Windows nodes
- Resource managers
- Resource metrics pipeline
- Resource Quotas
- ResourceAttributes — ResourceAttributes includes the authorization attributes available for resource requests to the Authorizer interface
- ResourceClaim — ResourceClaim describes a request for access to resources in the cluster, for use by workloads. For example, if a workload needs an accelerator device with specific properties, this is how that request is expressed. The status stanza tracks whether this claim has been satisfied and what specific resources have been allocated.
- ResourceClaimTemplate — ResourceClaimTemplate is used to produce ResourceClaim objects.
- ResourceHealthStatus
- ResourceLimitsPriorityFunction — ResourceLimitsPriorityFunction is a feature gate that enables the use of resource limits as a priority function.
- ResourcePoolStatusRequest — ResourcePoolStatusRequest triggers a one-time calculation of resource pool status based on the provided filters. Once status is set, the request is considered complete and will not be reprocessed. Users should delete and recreate requests to get updated information.
- ResourceQuota — ResourceQuota sets aggregate quota restrictions enforced per namespace
- ResourceQuotaScopeSelectors — ResourceQuotaScopeSelectors is a feature gate that allows you to scope resource quotas to specific namespaces or labels.
- ResourceRule — ResourceRule is the list of actions the subject is allowed to perform on resources. The list ordering isn't significant, may contain duplicates, and possibly be incomplete.
- ResourceSlice — ResourceSlice represents one or more resources in a pool of similar resources, managed by a common driver. A pool may span more than one ResourceSlice, and exactly how many ResourceSlices comprise a pool is determined by the driver. At the moment, the only supported resources are devices with attributes and capacities. Each device in a given pool, regardless of how many ResourceSlices, must have a unique name. The ResourceSlice in which a device gets published may change over time. The unique identifier for a device is the tuple <driver name>, <pool name>, <device name>. Whenever a driver needs to update a pool, it increments the pool.Spec.Pool.Generation number and updates all ResourceSlices with that new number and new resource definitions. A consumer must only use ResourceSlices with the highest generation number and ignore all others. When allocating all resources in a pool matching certain criteria or when looking for the best solution among several different alternatives, a consumer should check the number of ResourceSlices in a pool (included in each ResourceSlice) to determine whether its view of a pool is complete and if not, should wait until the driver has completed updating the pool. For resources that are not local to a node, the node name is not set. Instead, the driver may use a node selector to specify where the devices are available.
- RestartAllContainersOnContainerExits — RestartAllContainersOnContainerExits is a feature gate that restarts all containers when one container exits.
- Restrict a Container's Access to Resources with AppArmor
- Restrict a Container's Syscalls with seccomp
- RetroactiveDefaultStorageClass — RetroactiveDefaultStorageClass is a feature gate for automatically setting the default storage class in Kubernetes.
- RetryGenerateName — RetryGenerateName is a feature gate that controls the retry behavior for generating names.
- Role — Role is a namespaced, logical grouping of PolicyRules that can be referenced as a unit by a RoleBinding.
- Role Based Access Control Good Practices — Principles and practices for good RBAC design for cluster operators.
- RoleBinding — RoleBinding references a role, but does not contain it. It can reference a Role in the same namespace or a ClusterRole in the global namespace. It adds who information via Subjects and namespace information by which namespace it exists in. RoleBindings in a given namespace only have effect in that namespace.
- RoleRef — RoleRef contains information that points to the role being used
- Romana for NetworkPolicy
- RootCAConfigMap — RootCAConfigMap is a feature gate that enables or disables the use of a Root CA config map.
- RotateKubeletClientCertificate — RotateKubeletClientCertificate is a feature gate that enables the rotation of Kubelet client certificates.
- RotateKubeletServerCertificate — Rotates the Kubelet server certificate.
- RuleWithOperations — RuleWithOperations is a tuple of Operations and Resources. It is recommended to make sure that all the tuple expansions are valid.
- Run a Replicated Stateful Application
- Run a Single-Instance Stateful Application
- Run a Stateless Application Using a Deployment
- Run Applications — Run and manage both stateless and stateful applications.
- Run Jobs — Jobs in Kubernetes provide a way to run batch processing tasks, such as data imports or backups.
- RunAsGroup — RunAsGroup is a feature gate that enables or disables the ability to run pods as a specific group ID.
- Running Automated Tasks with a CronJob
- Running in multiple zones
- Running Kubelet in Standalone Mode
- Running Kubernetes Node Components as a Non-root User
- Running Multiple Instances of Your App
- Running Pods on Only Some Nodes
- Running ZooKeeper, A Distributed System Coordinator
- Runtime Class
- RuntimeClass — RuntimeClass defines a class of container runtime supported in the cluster. The RuntimeClass is used to determine which container runtime is used to run all containers in a pod. RuntimeClasses are manually defined by a user or cluster provisioner, and referenced in the PodSpec. The Kubelet is responsible for resolving the RuntimeClassName reference before running the pod. For more details, see https://kubernetes.io/docs/concepts/containers/runtime-class/
- RuntimeClass — Enables runtime class support for pods.
- RuntimeClassInImageCriApi — RuntimeClassInImageCriApi is a feature gate that allows the Kubernetes runtime class to be specified in the image cri-api.
- Safely Drain a Node
- Scale — Scale represents a scaling request for a resource.
- Scale a StatefulSet
- Scale Your App — Scale Your App to meet changing demands by adjusting resource allocation.
- Schedule GPUs — Configure and schedule GPUs for use as a resource by nodes in a cluster.
- ScheduleDaemonSetPods — Feature gate that enables scheduling DaemonSet pods.
- Scheduler Configuration
- Scheduler Performance Tuning
- SchedulerAsyncAPICalls — SchedulerAsyncAPICalls is a feature gate that enables the Kubernetes scheduler to make asynchronous API calls.
- SchedulerAsyncPreemption — SchedulerAsyncPreemption is a feature gate that enables asynchronous preemption.
- SchedulerPopFromBackoffQ — A feature gate for enabling or disabling the SchedulerPopFromBackoffQ feature.
- SchedulerQueueingHints — SchedulerQueueingHints is a feature gate that enables the Scheduler to use queueing hints for pod scheduling.
- Scheduling — Scheduling is a feature in Kubernetes that manages the placement of pods on nodes within a cluster.
- Scheduling — Scheduling is a Kubernetes feature that manages the allocation of resources to pods within the cluster.
- Scheduling Framework
- Scheduling Group
- Scheduling Policies
- Scheduling, Preemption and Eviction
- SCTPSupport — SCTPSupport is a feature gate that enables support for SCTP protocol in Kubernetes.
- Seccomp and Kubernetes
- SeccompDefault — SeccompDefault is a feature gate that enables the default seccomp profile in Kubernetes.
- Secret — Secret holds secret data of a certain type. The total bytes of the values in the Data field must be less than MaxSecretSize bytes.
- Secrets
- Securing a Cluster
- Security — Concepts for keeping your cloud-native workload secure.
- Security — Security encompasses measures taken to protect Kubernetes cluster resources from unauthorized access.
- Security Checklist — Baseline checklist for ensuring security in Kubernetes clusters.
- Security For Linux Nodes
- Security For Windows Nodes
- SecurityContextDeny — SecurityContextDeny is a feature gate that denies pods from running with privileged security contexts.
- SelectorIndex — A feature gate for enabling or disabling the SelectorIndex feature.
- SelfSubjectAccessReview — SelfSubjectAccessReview checks whether or the current user can perform an action. Not filling in a spec.namespace means "in all namespaces". Self is a special case, because users should always be able to check whether they can perform an action
- SelfSubjectReview — SelfSubjectReview contains the user information that the kube-apiserver has about the user making this request. When using impersonation, users will receive the user info of the user being impersonated. If impersonation or request header authentication is used, any extra keys will have their case ignored and returned as lowercase.
- SelfSubjectRulesReview — SelfSubjectRulesReview enumerates the set of actions the current user can perform within a namespace. The returned list of actions may be incomplete depending on the server's authorization mode, and any errors experienced during the evaluation. SelfSubjectRulesReview should be used by UIs to show/hide actions, or to quickly let an end user reason about their permissions. It should NOT Be used by external systems to drive authorization decisions as this raises confused deputy, cache lifetime/revocation, and correctness concerns. SubjectAccessReview, and LocalAccessReview are the correct way to defer authorization decisions to the API server.
- SELinuxChangePolicy — A feature gate that enables SELinux change policy for Kubernetes components.
- SELinuxMount — SELinuxMount is a feature gate that enables SELinux support for mounts.
- SELinuxMountReadWriteOncePod — A feature gate that enables SELinux mount with read-write once pod.
- SeparateCacheWatchRPC — SeparateCacheWatchRPC is a feature gate that enables separate cache watch RPCs.
- SeparateTaintEvictionController — SeparateTaintEvictionController is a feature gate that separates the taint eviction controller from the node controller.
- Server-Side Apply
- ServerAddressByClientCIDR — ServerAddressByClientCIDR helps the client to determine the server address that they should use, depending on the clientCIDR that they match.
- ServerSideApply — ServerSideApply is a feature gate that enables server-side apply functionality.
- ServerSideFieldValidation — ServerSideFieldValidation is a feature gate that controls whether server-side field validation is enabled.
- Service — Expose an application running in your cluster behind a single outward-facing endpoint, even when the workload is split across multiple backends.
- Service — Service is a named abstraction of software service (for example, mysql) consisting of local port (for example 3306) that the proxy listens on, and the selector that determines which pods will answer requests sent through the proxy.
- Service Accounts — Learn about ServiceAccount objects in Kubernetes.
- Service ClusterIP allocation
- Service Internal Traffic Policy — If two Pods in your cluster want to communicate, and both Pods are actually running on the same node, use _Service Internal Traffic Policy_ to keep network traffic within that node. Avoiding a round trip via the cluster network can help with reliability, performance (network latency and throughput), or cost.
- ServiceAccount — ServiceAccount binds together: * a name, understood by users, and perhaps by peripheral systems, for an identity * a principal that can be authenticated and authorized * a set of secrets
- ServiceAccountIssuerDiscovery — ServiceAccountIssuerDiscovery is a feature gate that enables service account issuer discovery.
- ServiceAccountNodeAudienceRestriction — A feature gate for service account node audience restriction.
- ServiceAccountTokenJTI — ServiceAccountTokenJTI is a feature gate that enables or disables Service Account Token JTI.
- ServiceAccountTokenNodeBinding — ServiceAccountTokenNodeBinding is a feature gate that enables node-level service account token binding.
- ServiceAccountTokenNodeBindingValidation — ServiceAccountTokenNodeBindingValidation is a feature gate that enables validation of service account token node bindings.
- ServiceAccountTokenPodNodeInfo — A feature gate that allows you to include pod node information in service account tokens.
- ServiceAppProtocol — Configures the protocol used for communication between services.
- ServiceCIDR — ServiceCIDR defines a range of IP addresses using CIDR format (e.g. 192.168.0.0/24 or 2001:db2::/64). This range is used to allocate ClusterIPs to Service objects.
- ServiceInternalTrafficPolicy — ServiceInternalTrafficPolicy is a feature gate that allows you to control how internal traffic is routed within a cluster.
- ServiceIPStaticSubrange — Service IP Static Subrange is a feature gate that enables the assignment of static IP addresses to services.
- ServiceLBNodePortControl — A feature gate that controls the node port range used by Service Load Balancers.
- ServiceLoadBalancerClass — A feature gate that enables the Service Load Balancer Class.
- ServiceLoadBalancerFinalizer — Enables the finalizer for Service LoadBalancers.
- ServiceNodeExclusion — Allows excluding nodes from the cluster.
- ServiceNodePortStaticSubrange — Enables static subranges for NodePorts.
- ServiceReference — ServiceReference holds a reference to Service.legacy.k8s.io
- Services — Abstraction layer for accessing and managing pods.
- Services, Load Balancing, and Networking — Concepts and resources behind networking in Kubernetes.
- ServiceTopology — Enables service topology awareness in Kubernetes.
- ServiceTrafficDistribution — Distributes service traffic across multiple endpoints.
- Set Kubelet Parameters Via A Configuration File
- Set up a High Availability etcd Cluster with kubeadm
- Set up an Extension API Server
- Set Up DRA in a Cluster
- Set up Konnectivity service
- SetHostnameAsFQDN — SetHostnameAsFQDN is a feature gate that allows setting the hostname as the fully qualified domain name (FQDN) in Kubernetes.
- Setup tools — A collection of setup tools and guides.
- ShardedListAndWatch — A feature gate that enables sharding for list and watch operations.
- ShardInfo — ShardInfo describes the shard selector that was applied to produce a list response. Its presence on a list response indicates the list is a filtered subset.
- Share a Cluster with Namespaces
- Share Process Namespace between Containers in a Pod
- Sidecar Containers
- SidecarContainers — Sidecar Containers is a feature gate that enables the use of sidecar containers in Kubernetes.
- SizeBasedListCostEstimate — SizeBasedListCostEstimate is a feature gate that enables cost estimation for Size-Based Autoscaling.
- SizeMemoryBackedVolumes — A feature gate that enables memory-backed volumes.
- SkipReadOnlyValidationGCE — SkipReadOnlyValidationGCE is a feature gate that skips read-only validation for Google Cloud Engine.
- Specifying a Disruption Budget for your Application
- StableLoadBalancerNodeSet — StableLoadBalancerNodeSet is a feature gate that enables stable load balancer node sets.
- StaleControllerConsistencyDaemonSet — A feature gate that enables the Stale Controller Consistency DaemonSet.
- StaleControllerConsistencyJob — StaleControllerConsistencyJob is a feature gate that enables stale controller consistency jobs in Kubernetes.
- StaleControllerConsistencyReplicaSet — StaleControllerConsistencyReplicaSet is a feature gate that enables stale controller consistency for ReplicaSets.
- StaleControllerConsistencyStatefulSet — StaleControllerConsistencyStatefulSet is a feature gate that ensures consistency between the controller and the stateful set.
- StartupProbe — StartupProbe is a feature gate for Kubernetes that enables probes to be executed during pod startup.
- Stateful Applications — Applications that require persistent storage and identity.
- StatefulSet — StatefulSet represents a set of pods with consistent identities. Identities are defined as: - Network: A single stable DNS and hostname. - Storage: As many VolumeClaims as requested. The StatefulSet guarantees that a given network identity will always map to the same storage identity.
- StatefulSet Basics
- StatefulSetAutoDeletePVC — StatefulSetAutoDeletePVC is a feature gate that enables automatic deletion of PVCs when a StatefulSet is deleted.
- StatefulSetMinReadySeconds — StatefulSetMinReadySeconds is a feature gate that sets the minimum number of seconds for a StatefulSet to be ready.
- StatefulSets — A StatefulSet runs a group of Pods, and maintains a sticky identity for each of those Pods. This is useful for managing applications that need persistent storage or a stable, unique network identity.
- StatefulSetStartOrdinal — A feature gate that allows specifying the start ordinal for StatefulSets.
- Stateless Applications — An application that does not store any data locally, relying on external services for storage.
- Static Pods
- Status — Status is a return value for calls that don't return other objects.
- StatusCause — StatusCause provides more information about an api.Status failure, including cases when multiple errors are encountered.
- StatusDetails — StatusDetails is a set of additional properties that MAY be set by the server to provide additional information about a response. The Reason field of a Status object defines what attributes will be set. Clients must ignore fields that do not match the defined type of each attribute, and should assume that any attribute may be empty, invalid, or under defined.
- Storage — Ways to provide both long-term and temporary storage to Pods in your cluster.
- Storage — Storage in Kubernetes refers to the management and organization of data storage resources.
- Storage Capacity
- Storage Classes
- Storage Versions
- StorageCapacityScoring
- StorageClass — StorageClass describes the parameters for a class of storage for which PersistentVolumes can be dynamically provisioned. StorageClasses are non-namespaced; the name of the storage class according to etcd is in ObjectMeta.Name.
- Storagemigration — Storagemigration is a Kubernetes API object that represents storage migration.
- StorageNamespaceIndex — Storage Namespace Index is a feature gate that enables the creation of an index for storage namespaces.
- StorageObjectInUseProtection — StorageObjectInUseProtection is a feature gate that enables protection against deleting or modifying storage objects in use.
- StorageVersion — Storage version of a specific resource.
- StorageVersionAPI — StorageVersionAPI is a feature gate that enables the use of storage version API.
- StorageVersionHash — Feature gate for enabling storage version hash.
- StorageVersionMigration — StorageVersionMigration represents a migration of stored data to the latest storage version.
- StorageVersionMigrator — StorageVersionMigrator is a feature gate that enables the migration of storage versions to ensure compatibility with newer Kubernetes versions.
- StreamingCollectionEncodingToJSON — A feature gate that enables streaming collection encoding to JSON.
- StreamingCollectionEncodingToProtobuf — Enables encoding of streaming collections to Protobuf format.
- StreamingProxyRedirects — StreamingProxyRedirects is a feature gate that controls the handling of redirects in streaming proxies.
- StrictCostEnforcementForVAP — StrictCostEnforcementForVAP is a feature gate that enforces strict cost accounting for Virtualized Attached Persistent (VAP) volumes.
- StrictCostEnforcementForWebhooks — StrictCostEnforcementForWebhooks enforces cost limits for webhooks.
- StrictIPCIDRValidation
- StructuredAuthenticationConfiguration — StructuredAuthenticationConfiguration is a feature gate that enables structured authentication configurations for pods.
- StructuredAuthenticationConfigurationEgressSelector — Allows for structured authentication configuration in Kubernetes.
- StructuredAuthenticationConfigurationJWKSMetrics — StructuredAuthenticationConfigurationJWKSMetrics is a feature gate that enables structured authentication configuration and JSON Web Key Set (JWS) metrics.
- StructuredAuthorizationConfiguration — A feature gate for structured authorization configuration.
- Subject — Subject contains a reference to the object or user identities a role binding applies to. This can either hold a direct API object reference, or a value for non-objects such as user and group names.
- SubjectAccessReview — SubjectAccessReview checks whether or not a user or group can perform an action.
- SubjectRulesReviewStatus — SubjectRulesReviewStatus contains the result of a rules check. This check can be incomplete depending on the set of authorizers the server is configured with and any errors experienced during evaluation. Because authorization rules are additive, if a rule appears in a list it's safe to assume the subject has that permission, even if that list is incomplete.
- SupplementalGroupsPolicy — A feature gate that enables supplemental groups policy.
- SupportIPVSProxyMode — SupportIPVSProxyMode is a feature gate that allows IPVS proxy mode to be enabled.
- SupportNodePidsLimit — Enable Support Node PIDs Limit to allow Kubernetes to limit the number of processes running on a node.
- SupportPodPidsLimit — A feature gate that enables or disables support for pod PIDs limit.
- SuspendJob — SuspendJob is a feature gate that allows for job suspension.
- Swap memory management
- Switching from Polling to CRI Event-based Updates to Container Status
- Sysctls — Sysctls is a feature gate that controls whether sysctl settings are applied to the Kubernetes control plane.
- System Logs
- SystemdWatchdog — SystemdWatchdog is a feature gate that enables the use of systemd's watchdog functionality in Kubernetes.
- TaintBasedEvictions — A feature gate for enabling taint-based evictions.
- TaintNodesByCondition — A feature gate that enables tainting nodes based on conditions.
- Taints and Tolerations
- TaintTolerationComparisonOperators — Adds comparison operators to taint and toleration.
- Tasks — Tasks are a way to perform specific actions on your Kubernetes cluster, such as deploying applications or managing resources.
- The kubectl command-line tool — kubectl is the primary command-line tool for communicating with a Kubernetes cluster. This page provides an overview of kubectl and its role in the Kubernetes ecosystem.
- The Kubernetes API — The Kubernetes API lets you query and manipulate the state of objects in Kubernetes. The core of Kubernetes' control plane is the API server and the HTTP API that it exposes. Users, the different parts of your cluster, and external components all communicate with one another through the API server.
- Time — Time is a wrapper around time.Time which supports correct marshaling to YAML and JSON. Wrappers are provided for many of the factory methods that the time package offers.
- TLS — Understand how to protect traffic within your cluster using Transport Layer Security (TLS).
- TLS bootstrapping
- TokenRequest — TokenRequest is a feature gate that controls the token request behavior.
- TokenRequestProjection — A feature gate that enables token request projection.
- TokenRequestServiceAccountUIDValidation — Enables validation of Service Account UIDs in Token Requests.
- TokenReview — TokenReview attempts to authenticate a token to a known user. Note: TokenReview requests may be cached by the webhook token authenticator plugin in the kube-apiserver.
- Toleration — The pod this Toleration is attached to tolerates any taint that matches the triple <key,value,effect> using the matching operator <operator>.
- Tools for Monitoring Resources
- Tools Included — Snippets to be included in the main kubectl-installs-*.md pages.
- Topology Aware Routing — _Topology Aware Routing_ provides a mechanism to help keep network traffic within the zone where it originated. Preferring same-zone traffic between Pods in your cluster can help with reliability, performance (network latency and throughput), or cost.
- Topology-Aware Workload Scheduling
- Topology-Aware Workload Scheduling
- TopologyAwareHints — TopologyAwareHints is a feature gate that enables topology-aware hints in Kubernetes.
- TopologyAwareWorkloadScheduling — Enable Topology Aware Workload Scheduling to allow Kubernetes to schedule pods based on node topology.
- TopologyManager — The TopologyManager is a feature gate that enables topology management in Kubernetes.
- TopologyManagerPolicyAlphaOptions — TopologyManagerPolicyAlphaOptions is a feature gate that enables alpha options for the Topology Manager policy.
- TopologyManagerPolicyBetaOptions — A feature gate for Topology Manager policy beta options.
- TopologyManagerPolicyOptions — TopologyManagerPolicyOptions is a feature gate that enables configuration of Topology Manager policy options.
- Traces For Kubernetes System Components
- Translate a Docker Compose File to Kubernetes Resources
- TranslateStreamCloseWebsocketRequests — Translate Stream Close Websocket Requests is a feature gate that enables translation of WebSocket close requests to HTTP requests.
- Troubleshooting Applications — Debugging common containerized application issues.
- Troubleshooting Clusters — Debugging common cluster issues.
- Troubleshooting CNI plugin-related errors
- Troubleshooting kubeadm
- Troubleshooting kubectl
- Troubleshooting Topology Management
- TTLAfterFinished — TTLAfterFinished is a feature gate that enables setting TTL (time-to-live) after a job has finished.
- Turnkey Cloud Solutions — Turnkey Cloud Solutions provide pre-configured, cloud-based environments for deploying and managing applications.
- Tutorials
- TypedLocalObjectReference — TypedLocalObjectReference contains enough information to let you locate the typed referenced object inside the same namespace.
- TypedLocalObjectReference — TypedLocalObjectReference allows to reference typed object inside the same namespace.
- UnauthenticatedHTTP2DOSMitigation — A feature gate that enables mitigation of HTTP/2 Denial-of-Service attacks without authentication.
- Understand Pressure Stall Information (PSI) Metrics — Detailed explanation of Pressure Stall Information (PSI) metrics and how to use them to identify resource pressure in Kubernetes.
- UnknownVersionInteroperabilityProxy — A feature gate that enables interoperability between different Kubernetes versions.
- UnlockWhileProcessingFIFO — UnlockWhileProcessingFIFO is a feature gate that enables unlocking of FIFO (First-In-First-Out) queues while processing.
- Update a Deployment Without Downtime
- Update API Objects in Place Using kubectl patch — Use kubectl patch to update Kubernetes API objects in place. Do a strategic merge patch or a JSON merge patch.
- Update Your App — Update Your App to ensure it remains secure, efficient, and aligned with changing business needs.
- Updating Configuration via a ConfigMap
- Upgrade A Cluster
- Upgrading kubeadm clusters
- Upgrading Linux nodes
- Upgrading Windows nodes
- Use a Service to Access an Application in a Cluster
- Use a SOCKS5 Proxy to Access the Kubernetes API
- Use a User Namespace With a Pod
- Use an HTTP Proxy to Access the Kubernetes API
- Use an Image Volume With a Pod
- Use Antrea for NetworkPolicy
- Use Calico for NetworkPolicy
- Use Cascading Deletion in a Cluster
- Use Cilium for NetworkPolicy
- Use Custom Resources — Custom Resources allow developers to define and manage custom objects within the Kubernetes cluster.
- Use Kube-router for NetworkPolicy
- Use Port Forwarding to Access Applications in a Cluster
- User Impersonation
- User Namespaces
- UserInfo — UserInfo holds the information about the user needed to implement the user.Info interface.
- UserNamespacesHostNetworkSupport — A feature gate that enables support for user namespaces on the host network.
- UserNamespacesPodSecurityStandards — UserNamespacesPodSecurityStandards is a feature gate that enables the use of user namespaces in pods.
- UserNamespacesStatelessPodsSupport — UserNamespacesStatelessPodsSupport is a feature gate that enables support for stateless pods in user namespaces.
- UserNamespacesSupport — UserNamespacesSupport enables the use of user namespaces in Kubernetes.
- Using a KMS provider for data encryption
- Using a Service to Expose Your App
- Using ABAC Authorization
- Using CoreDNS for Service Discovery
- Using kubectl to Create a Deployment
- Using Minikube to Create a Cluster
- Using Node Authorization
- Using NodeLocal DNSCache in Kubernetes Clusters
- Using RBAC Authorization
- Using Source IP
- Using sysctls in a Kubernetes Cluster
- Validate IPv4/IPv6 dual-stack
- Validate node setup
- ValidateProxyRedirects — A feature gate that enables validation of proxy redirects.
- Validating Admission Policy
- ValidatingAdmissionPolicy — ValidatingAdmissionPolicy describes the definition of an admission validation policy that accepts or rejects an object without changing it.
- ValidatingAdmissionPolicy — A feature gate for validating admission policy.
- ValidatingAdmissionPolicyBinding — ValidatingAdmissionPolicyBinding binds the ValidatingAdmissionPolicy with paramerized resources. ValidatingAdmissionPolicyBinding and parameter CRDs together define how cluster administrators configure policies for clusters. For a given admission request, each binding will cause its policy to be evaluated N times, where N is 1 for policies/bindings that don't use params, otherwise N is the number of parameters selected by the binding. The CEL expressions of a policy must have a computed CEL cost below the maximum CEL budget. Each evaluation of the policy is given an independent CEL cost budget. Adding/removing policies, bindings, or params can not affect whether a given (policy, binding, param) combination is within its own CEL budget.
- ValidatingWebhookConfiguration — ValidatingWebhookConfiguration describes the configuration of and admission webhook that accept or reject and object without changing it.
- Variable — Variable is the definition of a variable that is used for composition. A variable is defined as a named expression.
- verify kubectl install — How to verify kubectl.
- Verify Signed Kubernetes Artifacts
- Versions in CustomResourceDefinitions
- Vertical Pod Autoscaling
- Viewing Pods and Nodes
- Virtual IPs and Service Proxies
- Volume Attributes Classes
- Volume Health Monitoring
- Volume Populators and Data Sources
- Volume Snapshot Classes
- Volume Snapshots
- VolumeAttachment — VolumeAttachment captures the intent to attach or detach the specified volume to/from the specified node. VolumeAttachment objects are non-namespaced.
- VolumeAttributesClass — VolumeAttributesClass represents a specification of mutable volume attributes defined by the CSI driver. The class can be specified during dynamic provisioning of PersistentVolumeClaims, and changed in the PersistentVolumeClaim spec after provisioning.
- VolumeAttributesClass — A feature gate that allows specifying a class for volume attributes.
- VolumeCapacityPriority — VolumeCapacityPriority is a feature gate that allows volumes to be prioritized based on their capacity.
- VolumeLimitScaling — VolumeLimitScaling is a feature gate that enables or disables the scaling of volumes.
- VolumePVCDataSource — VolumePVCDataSource is a feature gate that enables the use of Persistent Volume Claims (PVCs) as data sources for volumes.
- Volumes
- VolumeScheduling — Enables volume scheduling for pods.
- VolumeSnapshotDataSource — VolumeSnapshotDataSource is a feature gate that enables volume snapshot data sources.
- VolumeSubpath — Volume Subpath is a feature gate that allows for the mounting of volumes at subpaths within a pod.
- VolumeSubpathEnvExpansion — Volume Subpath Env Expansion is a feature gate that enables the expansion of environment variables within subpaths.
- WarningHeaders — WarningHeaders allows for custom warning headers to be set in Kubernetes.
- WatchBookmark — WatchBookmark is a feature gate that enables bookmarking for watches.
- WatchCacheInitializationPostStartHook — A feature gate for enabling WatchCache initialization as a post-start hook.
- WatchEvent — Event represents a single event to a watched resource.
- WatchFromStorageWithoutResourceVersion — A feature gate that allows watching resources without a resource version.
- WatchList — A feature gate that enables or disables the WatchList API in Kubernetes.
- WatchListClient
- Weave Net for NetworkPolicy
- Webhook Mode
- WebhookAdmission Configuration (v1)
- WebhookClientConfig — WebhookClientConfig contains the information to make a TLS connection with the webhook
- Well-Known Labels, Annotations and Taints
- What Happens After A Node Restart
- What's next? — What's next after installing kubectl.
- Windows containers in Kubernetes
- Windows debugging tips
- Windows in Kubernetes — Kubernetes supports nodes that run Microsoft Windows.
- Windows Storage
- WindowsCPUAndMemoryAffinity — Windows CPU and Memory Affinity allows for more flexible placement of pods on Windows nodes.
- WindowsEndpointSliceProxying — Enables proxying of EndpointSlices on Windows nodes.
- WindowsGMSA — A feature gate for enabling or disabling WindowsGMSA support.
- WindowsGracefulNodeShutdown — WindowsGracefulNodeShutdown is a feature gate that enables graceful shutdown of nodes running Windows.
- WindowsHostNetwork — A feature gate that enables Windows host network support.
- WindowsHostProcessContainers — WindowsHostProcessContainers is a feature gate that enables or disables the use of Windows host process containers.
- WindowsRunAsUserName — A feature gate that allows you to run Kubernetes components as a specific Windows user.
- WinDSR — WinDSR is a feature gate that enables support for Windows DataSocket (DSR) protocol in Kubernetes.
- WinOverlay — WinOverlay is a feature gate that enables Windows overlay support.
- Workload — Workload allows for expressing scheduling constraints that should be used when managing the lifecycle of workloads from the scheduling perspective, including scheduling, preemption, eviction and other phases. Workload API enablement is toggled by the GenericWorkload feature gate.
- Workload API
- Workload Management
- Workload-Aware Preemption
- WorkloadAwarePreemption — WorkloadAwarePreemption is a feature gate that enables preemptive scheduling for workloads.
- Workloads — Understand Pods, the smallest deployable compute object in Kubernetes, and the higher-level abstractions that help you to run them.
- WorkloadWithJob — A feature gate that enables workloads with jobs.
- ZeroLimitedNominalConcurrencyShares — ZeroLimitedNominalConcurrencyShares is a feature gate that allows for the limitation of nominal concurrency shares.
- zsh auto-completion — Some optional configuration for zsh auto-completion.
Concepts (4800)
- _Deploy_ lifecycle phase {#lifecycle-phase-deploy}
- _Develop_ lifecycle phase {#lifecycle-phase-develop}
- _Distribute_ lifecycle phase {#lifecycle-phase-distribute}
- _Equality-based_ requirement
- _Runtime_ lifecycle phase {#lifecycle-phase-runtime}
- _Set-based_ requirement
- "410 Gone" responses
- (Optional) Configure a disruption budget {#configure-poddisruptionbudget}
- (Optional) Controlling your cluster from machines other than the control-plane node
- (Optional) Disable Leader Migration {#disable-leader-migration}
- (Optional) Proxying API Server to localhost
- [Aqua](https://www.aquasec.com)
- [Datadog](https://www.datadoghq.com/product/)
- [Dynatrace](https://www.dynatrace.com/)
- [Falco](https://falco.org)
- [Prisma Cloud Compute](https://docs.paloaltonetworks.com/prisma/prisma-cloud.html)
- [SignalFx (Splunk)](https://www.splunk.com/en_us/investor-relations/acquisitions/signalfx.html)
- {{% heading "cleanup" %}}
- {{% heading "envvars" %}}
- {{% heading "examples" %}}
- {{% heading "objectives" %}}
- {{% heading "options" %}}
- {{% heading "parentoptions" %}}
- {{% heading "prerequisites" %}}
- {{% heading "seealso" %}}
- {{% heading "synopsis" %}}
- {{% heading "whatsnext" %}}
- `/usr` is mounted read-only on nodes {#usr-mounted-read-only}
- `+k8s:alpha` {#tag-alpha}
- `+k8s:beta` {#tag-beta}
- `+k8s:eachKey` {#tag-eachKey}
- `+k8s:eachVal` {#tag-eachVal}
- `+k8s:enum` {#tag-enum}
- `+k8s:forbidden` {#tag-forbidden}
- `+k8s:format` {#tag-format}
- `+k8s:ifDisabled` {#tag-ifDisabled}
- `+k8s:ifEnabled` {#tag-ifEnabled}
- `+k8s:isSubresource` {#tag-isSubresource}
- `+k8s:item` {#tag-item}
- `+k8s:listMapKey` {#tag-listMapKey}
- `+k8s:listType` {#tag-listType}
- `+k8s:maxItems` {#tag-maxItems}
- `+k8s:maxLength` {#tag-maxLength}
- `+k8s:minimum` {#tag-minimum}
- `+k8s:neq` {#tag-neq}
- `+k8s:opaqueType` {#tag-opaqueType}
- `+k8s:optional` {#tag-optional}
- `+k8s:required` {#tag-required}
- `+k8s:subfield` {#tag-subfield}
- `+k8s:supportsSubresource` {#tag-supportsSubresource}
- `+k8s:unionDiscriminator` {#tag-unionDiscriminator}
- `+k8s:unionMember` {#tag-unionMember}
- `+k8s:zeroOrOneOfMember` {#tag-zeroOrOneOfMember}
- `AdmissionConfiguration` {#apiserver-config-k8s-io-v1-AdmissionConfiguration}
- `AdmissionConfiguration` {#apiserver-k8s-io-v1alpha1-AdmissionConfiguration}
- `AdmissionPluginConfiguration` {#apiserver-config-k8s-io-v1-AdmissionPluginConfiguration}
- `AdmissionPluginConfiguration` {#apiserver-k8s-io-v1alpha1-AdmissionPluginConfiguration}
- `AdmissionRequest` {#admission-k8s-io-v1-AdmissionRequest}
- `AdmissionResponse` {#admission-k8s-io-v1-AdmissionResponse}
- `AdmissionReview` {#admission-k8s-io-v1-AdmissionReview}
- `AESConfiguration` {#apiserver-config-k8s-io-v1-AESConfiguration}
- `AliasOverride` {#kubectl-config-k8s-io-v1alpha1-AliasOverride}
- `AliasOverride` {#kubectl-config-k8s-io-v1beta1-AliasOverride}
- `AllowlistEntry` {#kubectl-config-k8s-io-v1beta1-AllowlistEntry}
- `AnonymousAuthCondition` {#apiserver-config-k8s-io-v1-AnonymousAuthCondition}
- `AnonymousAuthCondition` {#apiserver-k8s-io-v1alpha1-AnonymousAuthCondition}
- `AnonymousAuthCondition` {#apiserver-k8s-io-v1beta1-AnonymousAuthCondition}
- `AnonymousAuthConfig` {#apiserver-config-k8s-io-v1-AnonymousAuthConfig}
- `AnonymousAuthConfig` {#apiserver-k8s-io-v1alpha1-AnonymousAuthConfig}
- `AnonymousAuthConfig` {#apiserver-k8s-io-v1beta1-AnonymousAuthConfig}
- `APIEndpoint` {#kubeadm-k8s-io-v1beta3-APIEndpoint}
- `APIEndpoint` {#kubeadm-k8s-io-v1beta4-APIEndpoint}
- `APIServer` {#kubeadm-k8s-io-v1beta3-APIServer}
- `APIServer` {#kubeadm-k8s-io-v1beta4-APIServer}
- `Arg` {#kubeadm-k8s-io-v1beta4-Arg}
- `AttachDetachControllerConfiguration` {#kubecontrollermanager-config-k8s-io-v1alpha1-AttachDetachControllerConfiguration}
- `AudienceMatchPolicyType` {#apiserver-config-k8s-io-v1-AudienceMatchPolicyType}
- `AudienceMatchPolicyType` {#apiserver-k8s-io-v1alpha1-AudienceMatchPolicyType}
- `AudienceMatchPolicyType` {#apiserver-k8s-io-v1beta1-AudienceMatchPolicyType}
- `AuthConfig` {#credentialprovider-kubelet-k8s-io-v1-AuthConfig}
- `AuthenticationConfiguration` {#apiserver-config-k8s-io-v1-AuthenticationConfiguration}
- `AuthenticationConfiguration` {#apiserver-k8s-io-v1alpha1-AuthenticationConfiguration}
- `AuthenticationConfiguration` {#apiserver-k8s-io-v1beta1-AuthenticationConfiguration}
- `AuthenticationMetadata` {#audit-k8s-io-v1-AuthenticationMetadata}
- `AuthInfo` {#AuthInfo}
- `AuthorizationConfiguration` {#apiserver-config-k8s-io-v1-AuthorizationConfiguration}
- `AuthorizationConfiguration` {#apiserver-k8s-io-v1alpha1-AuthorizationConfiguration}
- `AuthorizationConfiguration` {#apiserver-k8s-io-v1beta1-AuthorizationConfiguration}
- `AuthorizerConfiguration` {#apiserver-config-k8s-io-v1-AuthorizerConfiguration}
- `AuthorizerConfiguration` {#apiserver-k8s-io-v1alpha1-AuthorizerConfiguration}
- `AuthorizerConfiguration` {#apiserver-k8s-io-v1beta1-AuthorizerConfiguration}
- `AuthProviderConfig` {#AuthProviderConfig}
- `best-effort` policy {#policy-best-effort}
- `BootstrapToken` {#BootstrapToken}
- `BootstrapTokenDiscovery` {#kubeadm-k8s-io-v1beta3-BootstrapTokenDiscovery}
- `BootstrapTokenDiscovery` {#kubeadm-k8s-io-v1beta4-BootstrapTokenDiscovery}
- `BootstrapTokenString` {#BootstrapTokenString}
- `ClaimMappings` {#apiserver-config-k8s-io-v1-ClaimMappings}
- `ClaimMappings` {#apiserver-k8s-io-v1alpha1-ClaimMappings}
- `ClaimMappings` {#apiserver-k8s-io-v1beta1-ClaimMappings}
- `ClaimOrExpression` {#apiserver-config-k8s-io-v1-ClaimOrExpression}
- `ClaimOrExpression` {#apiserver-k8s-io-v1alpha1-ClaimOrExpression}
- `ClaimOrExpression` {#apiserver-k8s-io-v1beta1-ClaimOrExpression}
- `ClaimValidationRule` {#apiserver-config-k8s-io-v1-ClaimValidationRule}
- `ClaimValidationRule` {#apiserver-k8s-io-v1alpha1-ClaimValidationRule}
- `ClaimValidationRule` {#apiserver-k8s-io-v1beta1-ClaimValidationRule}
- `ClientConnectionConfiguration` {#ClientConnectionConfiguration}
- `CloudControllerManagerConfiguration` {#cloudcontrollermanager-config-k8s-io-v1alpha1-CloudControllerManagerConfiguration}
- `CloudProviderConfiguration` {#cloudcontrollermanager-config-k8s-io-v1alpha1-CloudProviderConfiguration}
- `Cluster` {#client-authentication-k8s-io-v1-Cluster}
- `Cluster` {#client-authentication-k8s-io-v1beta1-Cluster}
- `Cluster` {#Cluster}
- `ClusterConfiguration` {#kubeadm-k8s-io-v1beta3-ClusterConfiguration}
- `ClusterConfiguration` {#kubeadm-k8s-io-v1beta4-ClusterConfiguration}
- `CommandDefaults` {#kubectl-config-k8s-io-v1alpha1-CommandDefaults}
- `CommandDefaults` {#kubectl-config-k8s-io-v1beta1-CommandDefaults}
- `CommandOptionDefault` {#kubectl-config-k8s-io-v1alpha1-CommandOptionDefault}
- `CommandOptionDefault` {#kubectl-config-k8s-io-v1beta1-CommandOptionDefault}
- `Config` {#Config}
- `Configuration` {#eventratelimit-admission-k8s-io-v1alpha1-Configuration}
- `Connection` {#apiserver-k8s-io-v1alpha1-Connection}
- `Connection` {#apiserver-k8s-io-v1beta1-Connection}
- `container` scope
- `ContainerMetrics` {#metrics-k8s-io-v1beta1-ContainerMetrics}
- `Context` {#Context}
- `ControllerLeaderConfiguration` {#controllermanager-config-k8s-io-v1alpha1-ControllerLeaderConfiguration}
- `ControlPlaneComponent` {#kubeadm-k8s-io-v1beta3-ControlPlaneComponent}
- `ControlPlaneComponent` {#kubeadm-k8s-io-v1beta4-ControlPlaneComponent}
- `coredns` is stuck in the `Pending` state
- `coredns` pods have `CrashLoopBackOff` or `Error` state
- `CrashLoopBackOffConfig` {#kubelet-config-k8s-io-v1beta1-CrashLoopBackOffConfig}
- `CredentialPluginPolicy` {#kubectl-config-k8s-io-v1beta1-CredentialPluginPolicy}
- `CredentialProvider` {#kubelet-config-k8s-io-v1-CredentialProvider}
- `CredentialProvider` {#kubelet-config-k8s-io-v1alpha1-CredentialProvider}
- `CredentialProvider` {#kubelet-config-k8s-io-v1beta1-CredentialProvider}
- `CredentialProviderConfig` {#kubelet-config-k8s-io-v1-CredentialProviderConfig}
- `CredentialProviderConfig` {#kubelet-config-k8s-io-v1alpha1-CredentialProviderConfig}
- `CredentialProviderConfig` {#kubelet-config-k8s-io-v1beta1-CredentialProviderConfig}
- `CredentialProviderRequest` {#credentialprovider-kubelet-k8s-io-v1-CredentialProviderRequest}
- `CredentialProviderResponse` {#credentialprovider-kubelet-k8s-io-v1-CredentialProviderResponse}
- `CronJobControllerConfiguration` {#kubecontrollermanager-config-k8s-io-v1alpha1-CronJobControllerConfiguration}
- `CSRSigningConfiguration` {#kubecontrollermanager-config-k8s-io-v1alpha1-CSRSigningConfiguration}
- `CSRSigningControllerConfiguration` {#kubecontrollermanager-config-k8s-io-v1alpha1-CSRSigningControllerConfiguration}
- `DaemonSetControllerConfiguration` {#kubecontrollermanager-config-k8s-io-v1alpha1-DaemonSetControllerConfiguration}
- `DebuggingConfiguration` {#DebuggingConfiguration}
- `DefaultPreemptionArgs` {#kubescheduler-config-k8s-io-v1-DefaultPreemptionArgs}
- `delete` Delete
- `delete` Delete Collection
- `delete` Delete Connect Proxy
- `delete` Delete Connect Proxy Path
- `DeploymentControllerConfiguration` {#kubecontrollermanager-config-k8s-io-v1alpha1-DeploymentControllerConfiguration}
- `DeprecatedControllerConfiguration` {#kubecontrollermanager-config-k8s-io-v1alpha1-DeprecatedControllerConfiguration}
- `DetectLocalConfiguration` {#kubeproxy-config-k8s-io-v1alpha1-DetectLocalConfiguration}
- `DeviceTaintEvictionControllerConfiguration` {#kubecontrollermanager-config-k8s-io-v1alpha1-DeviceTaintEvictionControllerConfiguration}
- `Discovery` {#kubeadm-k8s-io-v1beta3-Discovery}
- `Discovery` {#kubeadm-k8s-io-v1beta4-Discovery}
- `DisruptionTarget`
- `DNS` {#kubeadm-k8s-io-v1beta3-DNS}
- `DNS` {#kubeadm-k8s-io-v1beta4-DNS}
- `DynamicResourcesArgs` {#kubescheduler-config-k8s-io-v1-DynamicResourcesArgs}
- `ebtables` or some similar executable not found during installation
- `EgressSelection` {#apiserver-k8s-io-v1alpha1-EgressSelection}
- `EgressSelection` {#apiserver-k8s-io-v1beta1-EgressSelection}
- `EgressSelectorConfiguration` {#apiserver-k8s-io-v1alpha1-EgressSelectorConfiguration}
- `EgressSelectorConfiguration` {#apiserver-k8s-io-v1beta1-EgressSelectorConfiguration}
- `EgressSelectorType` {#apiserver-config-k8s-io-v1-EgressSelectorType}
- `EgressSelectorType` {#apiserver-k8s-io-v1alpha1-EgressSelectorType}
- `EgressSelectorType` {#apiserver-k8s-io-v1beta1-EgressSelectorType}
- `EncryptionAlgorithmType` {#kubeadm-k8s-io-v1beta4-EncryptionAlgorithmType}
- `EncryptionConfiguration` {#apiserver-config-k8s-io-v1-EncryptionConfiguration}
- `EndpointControllerConfiguration` {#kubecontrollermanager-config-k8s-io-v1alpha1-EndpointControllerConfiguration}
- `EndpointSliceControllerConfiguration` {#kubecontrollermanager-config-k8s-io-v1alpha1-EndpointSliceControllerConfiguration}
- `EndpointSliceMirroringControllerConfiguration` {#kubecontrollermanager-config-k8s-io-v1alpha1-EndpointSliceMirroringControllerConfiguration}
- `EnvVar` {#kubeadm-k8s-io-v1beta4-EnvVar}
- `EphemeralVolumeControllerConfiguration` {#kubecontrollermanager-config-k8s-io-v1alpha1-EphemeralVolumeControllerConfiguration}
- `Etcd` {#kubeadm-k8s-io-v1beta3-Etcd}
- `Etcd` {#kubeadm-k8s-io-v1beta4-Etcd}
- `Event` {#audit-k8s-io-v1-Event}
- `EventList` {#audit-k8s-io-v1-EventList}
- `ExecConfig` {#ExecConfig}
- `ExecCredential` {#client-authentication-k8s-io-v1-ExecCredential}
- `ExecCredential` {#client-authentication-k8s-io-v1beta1-ExecCredential}
- `ExecCredentialSpec` {#client-authentication-k8s-io-v1-ExecCredentialSpec}
- `ExecCredentialSpec` {#client-authentication-k8s-io-v1beta1-ExecCredentialSpec}
- `ExecCredentialStatus` {#client-authentication-k8s-io-v1-ExecCredentialStatus}
- `ExecCredentialStatus` {#client-authentication-k8s-io-v1beta1-ExecCredentialStatus}
- `ExecEnvVar` {#ExecEnvVar}
- `ExecEnvVar` {#kubelet-config-k8s-io-v1-ExecEnvVar}
- `ExecEnvVar` {#kubelet-config-k8s-io-v1alpha1-ExecEnvVar}
- `ExecEnvVar` {#kubelet-config-k8s-io-v1beta1-ExecEnvVar}
- `ExecInteractiveMode` {#ExecInteractiveMode}
- `Extender` {#kubescheduler-config-k8s-io-v1-Extender}
- `ExtenderManagedResource` {#kubescheduler-config-k8s-io-v1-ExtenderManagedResource}
- `ExtenderTLSConfig` {#kubescheduler-config-k8s-io-v1-ExtenderTLSConfig}
- `ExternalEtcd` {#kubeadm-k8s-io-v1beta3-ExternalEtcd}
- `ExternalEtcd` {#kubeadm-k8s-io-v1beta4-ExternalEtcd}
- `ExternalMetricValue` {#external-metrics-k8s-io-v1beta1-ExternalMetricValue}
- `ExternalMetricValueList` {#external-metrics-k8s-io-v1beta1-ExternalMetricValueList}
- `ExtraMapping` {#apiserver-config-k8s-io-v1-ExtraMapping}
- `ExtraMapping` {#apiserver-k8s-io-v1alpha1-ExtraMapping}
- `ExtraMapping` {#apiserver-k8s-io-v1beta1-ExtraMapping}
- `FileDiscovery` {#kubeadm-k8s-io-v1beta3-FileDiscovery}
- `FileDiscovery` {#kubeadm-k8s-io-v1beta4-FileDiscovery}
- `FormatOptions` {#FormatOptions}
- `GarbageCollectorControllerConfiguration` {#kubecontrollermanager-config-k8s-io-v1alpha1-GarbageCollectorControllerConfiguration}
- `GenericControllerManagerConfiguration` {#controllermanager-config-k8s-io-v1alpha1-GenericControllerManagerConfiguration}
- `get` Get Connect Attach
- `get` Get Connect Exec
- `get` Get Connect Portforward
- `get` Get Connect Proxy
- `get` Get Connect Proxy Path
- `Get` gRPC endpoint {#grpc-endpoint-get}
- `get` List
- `get` List All Namespaces
- `get` Read
- `get` Read EphemeralContainers
- `get` Read Log
- `get` Read Resize
- `get` Read Scale
- `get` Read Status
- `get` Watch
- `get` Watch List
- `get` Watch List All Namespaces
- `GetAllocatableResources` gRPC endpoint {#grpc-endpoint-getallocatableresources}
- `GetPod` {#get-pod}
- `GroupResource` {#kubecontrollermanager-config-k8s-io-v1alpha1-GroupResource}
- `GroupResources` {#audit-k8s-io-v1-GroupResources}
- `head` Head Connect Proxy
- `head` Head Connect Proxy Path
- `HostPathMount` {#kubeadm-k8s-io-v1beta3-HostPathMount}
- `HostPathMount` {#kubeadm-k8s-io-v1beta4-HostPathMount}
- `HostPort` services do not work
- `HPAControllerConfiguration` {#kubecontrollermanager-config-k8s-io-v1alpha1-HPAControllerConfiguration}
- `IdentityConfiguration` {#apiserver-config-k8s-io-v1-IdentityConfiguration}
- `ImageMeta` {#kubeadm-k8s-io-v1beta3-ImageMeta}
- `ImageMeta` {#kubeadm-k8s-io-v1beta4-ImageMeta}
- `ImagePullCredentials` {#kubelet-config-k8s-io-v1alpha1-ImagePullCredentials}
- `ImagePullCredentials` {#kubelet-config-k8s-io-v1beta1-ImagePullCredentials}
- `ImagePullCredentialsVerificationPolicy` {#kubelet-config-k8s-io-v1beta1-ImagePullCredentialsVerificationPolicy}
- `ImagePulledRecord` {#kubelet-config-k8s-io-v1alpha1-ImagePulledRecord}
- `ImagePulledRecord` {#kubelet-config-k8s-io-v1beta1-ImagePulledRecord}
- `ImagePullIntent` {#kubelet-config-k8s-io-v1alpha1-ImagePullIntent}
- `ImagePullIntent` {#kubelet-config-k8s-io-v1beta1-ImagePullIntent}
- `ImagePullSecret` {#kubelet-config-k8s-io-v1alpha1-ImagePullSecret}
- `ImagePullSecret` {#kubelet-config-k8s-io-v1beta1-ImagePullSecret}
- `ImagePullServiceAccount` {#kubelet-config-k8s-io-v1alpha1-ImagePullServiceAccount}
- `ImagePullServiceAccount` {#kubelet-config-k8s-io-v1beta1-ImagePullServiceAccount}
- `ImageReview` {#imagepolicy-k8s-io-v1alpha1-ImageReview}
- `ImageReviewContainerSpec` {#imagepolicy-k8s-io-v1alpha1-ImageReviewContainerSpec}
- `ImageReviewSpec` {#imagepolicy-k8s-io-v1alpha1-ImageReviewSpec}
- `ImageReviewStatus` {#imagepolicy-k8s-io-v1alpha1-ImageReviewStatus}
- `InitConfiguration` {#kubeadm-k8s-io-v1beta3-InitConfiguration}
- `InitConfiguration` {#kubeadm-k8s-io-v1beta4-InitConfiguration}
- `InterPodAffinityArgs` {#kubescheduler-config-k8s-io-v1-InterPodAffinityArgs}
- `iptables` proxy mode {#proxy-mode-iptables}
- `Issuer` {#apiserver-config-k8s-io-v1-Issuer}
- `Issuer` {#apiserver-k8s-io-v1alpha1-Issuer}
- `Issuer` {#apiserver-k8s-io-v1beta1-Issuer}
- `JobControllerConfiguration` {#kubecontrollermanager-config-k8s-io-v1alpha1-JobControllerConfiguration}
- `JoinConfiguration` {#kubeadm-k8s-io-v1beta3-JoinConfiguration}
- `JoinConfiguration` {#kubeadm-k8s-io-v1beta4-JoinConfiguration}
- `JoinControlPlane` {#kubeadm-k8s-io-v1beta3-JoinControlPlane}
- `JoinControlPlane` {#kubeadm-k8s-io-v1beta4-JoinControlPlane}
- `JSONOptions` {#JSONOptions}
- `JWTAuthenticator` {#apiserver-config-k8s-io-v1-JWTAuthenticator}
- `JWTAuthenticator` {#apiserver-k8s-io-v1alpha1-JWTAuthenticator}
- `JWTAuthenticator` {#apiserver-k8s-io-v1beta1-JWTAuthenticator}
- `kernelspace` proxy mode {#proxy-mode-kernelspace}
- `Key` {#apiserver-config-k8s-io-v1-Key}
- `KMSConfiguration` {#apiserver-config-k8s-io-v1-KMSConfiguration}
- `kompose convert`
- `kube-controller-manager` metrics
- `kube-scheduler` metrics
- `kubeadm reset` unmounts `/var/lib/kubelet`
- `kubeadm upgrade plan` prints out `context deadline exceeded` error message
- `KubeCloudSharedConfiguration` {#cloudcontrollermanager-config-k8s-io-v1alpha1-KubeCloudSharedConfiguration}
- `KubeControllerManagerConfiguration` {#kubecontrollermanager-config-k8s-io-v1alpha1-KubeControllerManagerConfiguration}
- `kubectl auth reconcile` {#kubectl-auth-reconcile}
- `kubectl create clusterrole`
- `kubectl create clusterrolebinding`
- `kubectl create role`
- `kubectl create rolebinding`
- `kubectl proxy`
- `kubectl run`
- `kubelet` metrics
- `KubeletAnonymousAuthentication` {#kubelet-config-k8s-io-v1beta1-KubeletAnonymousAuthentication}
- `KubeletAuthentication` {#kubelet-config-k8s-io-v1beta1-KubeletAuthentication}
- `KubeletAuthorization` {#kubelet-config-k8s-io-v1beta1-KubeletAuthorization}
- `KubeletAuthorizationMode` {#kubelet-config-k8s-io-v1beta1-KubeletAuthorizationMode}
- `KubeletConfiguration` {#kubelet-config-k8s-io-v1beta1-KubeletConfiguration}
- `KubeletWebhookAuthentication` {#kubelet-config-k8s-io-v1beta1-KubeletWebhookAuthentication}
- `KubeletWebhookAuthorization` {#kubelet-config-k8s-io-v1beta1-KubeletWebhookAuthorization}
- `KubeletX509Authentication` {#kubelet-config-k8s-io-v1beta1-KubeletX509Authentication}
- `KubeProxyConfiguration` {#kubeproxy-config-k8s-io-v1alpha1-KubeProxyConfiguration}
- `KubeProxyConntrackConfiguration` {#kubeproxy-config-k8s-io-v1alpha1-KubeProxyConntrackConfiguration}
- `KubeProxyIPTablesConfiguration` {#kubeproxy-config-k8s-io-v1alpha1-KubeProxyIPTablesConfiguration}
- `KubeProxyIPVSConfiguration` {#kubeproxy-config-k8s-io-v1alpha1-KubeProxyIPVSConfiguration}
- `KubeProxyNFTablesConfiguration` {#kubeproxy-config-k8s-io-v1alpha1-KubeProxyNFTablesConfiguration}
- `KubeProxyWinkernelConfiguration` {#kubeproxy-config-k8s-io-v1alpha1-KubeProxyWinkernelConfiguration}
- `KubeSchedulerConfiguration` {#kubescheduler-config-k8s-io-v1-KubeSchedulerConfiguration}
- `KubeSchedulerProfile` {#kubescheduler-config-k8s-io-v1-KubeSchedulerProfile}
- `LeaderElectionConfiguration` {#LeaderElectionConfiguration}
- `LeaderMigrationConfiguration` {#controllermanager-config-k8s-io-v1alpha1-LeaderMigrationConfiguration}
- `LegacySATokenCleanerConfiguration` {#kubecontrollermanager-config-k8s-io-v1alpha1-LegacySATokenCleanerConfiguration}
- `Level` {#audit-k8s-io-v1-Level}
- `Limit` {#eventratelimit-admission-k8s-io-v1alpha1-Limit}
- `LimitType` {#eventratelimit-admission-k8s-io-v1alpha1-LimitType}
- `List` gRPC endpoint {#grpc-endpoint-list}
- `ListPods` {#list-pods}
- `LocalEtcd` {#kubeadm-k8s-io-v1beta3-LocalEtcd}
- `LocalEtcd` {#kubeadm-k8s-io-v1beta4-LocalEtcd}
- `Localhost` profiles
- `LocalMode` {#kubeproxy-config-k8s-io-v1alpha1-LocalMode}
- `LogFormatFactory` {#LogFormatFactory}
- `LoggingConfiguration` {#LoggingConfiguration}
- `LoggingOptions` {#LoggingOptions}
- `max-allowable-numa-nodes` {#policy-option-max-allowable-numa-nodes}
- `MemoryReservation` {#kubelet-config-k8s-io-v1beta1-MemoryReservation}
- `MemoryReservationPolicy` {#kubelet-config-k8s-io-v1beta1-MemoryReservationPolicy}
- `MemorySwapConfiguration` {#kubelet-config-k8s-io-v1beta1-MemorySwapConfiguration}
- `MetricIdentifier` {#custom-metrics-k8s-io-v1beta2-MetricIdentifier}
- `MetricListOptions` {#custom-metrics-k8s-io-v1beta2-MetricListOptions}
- `MetricValue` {#custom-metrics-k8s-io-v1beta2-MetricValue}
- `MetricValueList` {#custom-metrics-k8s-io-v1beta2-MetricValueList}
- `NamedAuthInfo` {#NamedAuthInfo}
- `NamedCluster` {#NamedCluster}
- `NamedContext` {#NamedContext}
- `NamedExtension` {#NamedExtension}
- `NamespaceControllerConfiguration` {#kubecontrollermanager-config-k8s-io-v1alpha1-NamespaceControllerConfiguration}
- `Networking` {#kubeadm-k8s-io-v1beta3-Networking}
- `Networking` {#kubeadm-k8s-io-v1beta4-Networking}
- `nftables` proxy mode {#proxy-mode-nftables}
- `NodeAffinityArgs` {#kubescheduler-config-k8s-io-v1-NodeAffinityArgs}
- `NodeControllerConfiguration` {#NodeControllerConfiguration}
- `NodeIPAMControllerConfiguration` {#kubecontrollermanager-config-k8s-io-v1alpha1-NodeIPAMControllerConfiguration}
- `NodeLifecycleControllerConfiguration` {#kubecontrollermanager-config-k8s-io-v1alpha1-NodeLifecycleControllerConfiguration}
- `NodeMetrics` {#metrics-k8s-io-v1beta1-NodeMetrics}
- `NodeMetricsList` {#metrics-k8s-io-v1beta1-NodeMetricsList}
- `NodeRegistrationOptions` {#kubeadm-k8s-io-v1beta3-NodeRegistrationOptions}
- `NodeRegistrationOptions` {#kubeadm-k8s-io-v1beta4-NodeRegistrationOptions}
- `NodeResourcesBalancedAllocationArgs` {#kubescheduler-config-k8s-io-v1-NodeResourcesBalancedAllocationArgs}
- `NodeResourcesFitArgs` {#kubescheduler-config-k8s-io-v1-NodeResourcesFitArgs}
- `none` policy {#policy-none}
- `none` policy configuration
- `ObjectReference` {#audit-k8s-io-v1-ObjectReference}
- `Operation` {#admission-k8s-io-v1-Operation}
- `OutputRoutingOptions` {#OutputRoutingOptions}
- `patch` Patch
- `patch` Patch EphemeralContainers
- `patch` Patch Resize
- `patch` Patch Scale
- `patch` Patch Status
- `Patches` {#kubeadm-k8s-io-v1beta3-Patches}
- `Patches` {#kubeadm-k8s-io-v1beta4-Patches}
- `PatchType` {#admission-k8s-io-v1-PatchType}
- `PersistentVolumeBinderControllerConfiguration` {#kubecontrollermanager-config-k8s-io-v1alpha1-PersistentVolumeBinderControllerConfiguration}
- `PersistentVolumeRecyclerConfiguration` {#kubecontrollermanager-config-k8s-io-v1alpha1-PersistentVolumeRecyclerConfiguration}
- `Plugin` {#kubescheduler-config-k8s-io-v1-Plugin}
- `PluginCacheKeyType` {#credentialprovider-kubelet-k8s-io-v1-PluginCacheKeyType}
- `PluginConfig` {#kubescheduler-config-k8s-io-v1-PluginConfig}
- `Plugins` {#kubescheduler-config-k8s-io-v1-Plugins}
- `PluginSet` {#kubescheduler-config-k8s-io-v1-PluginSet}
- `pod` scope
- `PodGCControllerConfiguration` {#kubecontrollermanager-config-k8s-io-v1alpha1-PodGCControllerConfiguration}
- `PodGroupScheduled`
- `PodMetrics` {#metrics-k8s-io-v1beta1-PodMetrics}
- `PodMetricsList` {#metrics-k8s-io-v1beta1-PodMetricsList}
- `PodTopologySpreadArgs` {#kubescheduler-config-k8s-io-v1-PodTopologySpreadArgs}
- `PodTopologySpreadConstraintsDefaulting` {#kubescheduler-config-k8s-io-v1-PodTopologySpreadConstraintsDefaulting}
- `Policy` {#audit-k8s-io-v1-Policy}
- `PolicyList` {#audit-k8s-io-v1-PolicyList}
- `PolicyRule` {#audit-k8s-io-v1-PolicyRule}
- `post` checkpoint the specified container {#post-checkpoint}
- `post` Create
- `post` Create Connect Attach
- `post` Create Connect Exec
- `post` Create Connect Portforward
- `post` Create Connect Proxy
- `post` Create Connect Proxy Path
- `post` Create Eviction
- `prefer-closest-numa-nodes` {#policy-option-prefer-closest-numa-nodes}
- `Preference` {#kubectl-config-k8s-io-v1alpha1-Preference}
- `Preference` {#kubectl-config-k8s-io-v1beta1-Preference}
- `Preferences` {#Preferences}
- `PrefixedClaimOrExpression` {#apiserver-config-k8s-io-v1-PrefixedClaimOrExpression}
- `PrefixedClaimOrExpression` {#apiserver-k8s-io-v1alpha1-PrefixedClaimOrExpression}
- `PrefixedClaimOrExpression` {#apiserver-k8s-io-v1beta1-PrefixedClaimOrExpression}
- `ProtocolType` {#apiserver-k8s-io-v1alpha1-ProtocolType}
- `ProtocolType` {#apiserver-k8s-io-v1beta1-ProtocolType}
- `ProviderConfiguration` {#apiserver-config-k8s-io-v1-ProviderConfiguration}
- `Proxy` {#kubeadm-k8s-io-v1beta4-Proxy}
- `ProxyMode` {#kubeproxy-config-k8s-io-v1alpha1-ProxyMode}
- `put` Replace
- `put` Replace Connect Proxy
- `put` Replace Connect Proxy Path
- `put` Replace EphemeralContainers
- `put` Replace Resize
- `put` Replace Scale
- `put` Replace Status
- `ReplicaSetControllerConfiguration` {#kubecontrollermanager-config-k8s-io-v1alpha1-ReplicaSetControllerConfiguration}
- `ReplicationControllerConfiguration` {#kubecontrollermanager-config-k8s-io-v1alpha1-ReplicationControllerConfiguration}
- `RequestedToCapacityRatioParam` {#kubescheduler-config-k8s-io-v1-RequestedToCapacityRatioParam}
- `ResetConfiguration` {#kubeadm-k8s-io-v1beta4-ResetConfiguration}
- `ResourceChangeDetectionStrategy` {#kubelet-config-k8s-io-v1beta1-ResourceChangeDetectionStrategy}
- `ResourceClaimControllerConfiguration` {#kubecontrollermanager-config-k8s-io-v1alpha1-ResourceClaimControllerConfiguration}
- `ResourceConfiguration` {#apiserver-config-k8s-io-v1-ResourceConfiguration}
- `ResourceQuotaControllerConfiguration` {#kubecontrollermanager-config-k8s-io-v1alpha1-ResourceQuotaControllerConfiguration}
- `ResourceSpec` {#kubescheduler-config-k8s-io-v1-ResourceSpec}
- `resourceVersion` fields in metadata {#resourceversion-in-metadata}
- `resourceVersion` parameters in query strings {#the-resourceversion-parameter}
- `restricted` policy {#policy-restricted}
- `Running` {#container-state-running}
- `SAControllerConfiguration` {#kubecontrollermanager-config-k8s-io-v1alpha1-SAControllerConfiguration}
- `ScoringStrategy` {#kubescheduler-config-k8s-io-v1-ScoringStrategy}
- `ScoringStrategyType` {#kubescheduler-config-k8s-io-v1-ScoringStrategyType}
- `SCTP` {#protocol-sctp}
- `SecretboxConfiguration` {#apiserver-config-k8s-io-v1-SecretboxConfiguration}
- `SerializedNodeConfigSource` {#kubelet-config-k8s-io-v1beta1-SerializedNodeConfigSource}
- `ServiceAccountTokenAttributes` {#kubelet-config-k8s-io-v1-ServiceAccountTokenAttributes}
- `ServiceAccountTokenCacheType` {#kubelet-config-k8s-io-v1-ServiceAccountTokenCacheType}
- `ServiceControllerConfiguration` {#ServiceControllerConfiguration}
- `ShutdownGracePeriodByPodPriority` {#kubelet-config-k8s-io-v1beta1-ShutdownGracePeriodByPodPriority}
- `single-numa-node` policy {#policy-single-numa-node}
- `Stage` {#audit-k8s-io-v1-Stage}
- `StatefulSetControllerConfiguration` {#kubecontrollermanager-config-k8s-io-v1alpha1-StatefulSetControllerConfiguration}
- `static` policy configuration
- `TCP` {#protocol-tcp}
- `TCPTransport` {#apiserver-k8s-io-v1alpha1-TCPTransport}
- `TCPTransport` {#apiserver-k8s-io-v1beta1-TCPTransport}
- `Terminated` {#container-state-terminated}
- `TextOptions` {#TextOptions}
- `TimeOrMetaDuration` {#TimeOrMetaDuration}
- `Timeouts` {#kubeadm-k8s-io-v1beta4-Timeouts}
- `TLSConfig` {#apiserver-k8s-io-v1alpha1-TLSConfig}
- `TLSConfig` {#apiserver-k8s-io-v1beta1-TLSConfig}
- `topologySpreadConstraints` field
- `TracingConfiguration` {#apiserver-config-k8s-io-v1-TracingConfiguration}
- `TracingConfiguration` {#apiserver-k8s-io-v1alpha1-TracingConfiguration}
- `TracingConfiguration` {#apiserver-k8s-io-v1beta1-TracingConfiguration}
- `TracingConfiguration` {#TracingConfiguration}
- `Transport` {#apiserver-k8s-io-v1alpha1-Transport}
- `Transport` {#apiserver-k8s-io-v1beta1-Transport}
- `TTLAfterFinishedControllerConfiguration` {#kubecontrollermanager-config-k8s-io-v1alpha1-TTLAfterFinishedControllerConfiguration}
- `type: ClusterIP` {#type-clusterip}
- `type: ExternalName` {#externalname}
- `type: LoadBalancer` {#loadbalancer}
- `type: NodePort` {#type-nodeport}
- `UDP` {#protocol-udp}
- `UDSTransport` {#apiserver-k8s-io-v1alpha1-UDSTransport}
- `UDSTransport` {#apiserver-k8s-io-v1beta1-UDSTransport}
- `UpgradeApplyConfiguration` {#kubeadm-k8s-io-v1beta4-UpgradeApplyConfiguration}
- `UpgradeConfiguration` {#kubeadm-k8s-io-v1beta4-UpgradeConfiguration}
- `UpgradeDiffConfiguration` {#kubeadm-k8s-io-v1beta4-UpgradeDiffConfiguration}
- `UpgradeNodeConfiguration` {#kubeadm-k8s-io-v1beta4-UpgradeNodeConfiguration}
- `UpgradePlanConfiguration` {#kubeadm-k8s-io-v1beta4-UpgradePlanConfiguration}
- `UserNamespaces` {#kubelet-config-k8s-io-v1beta1-UserNamespaces}
- `UserValidationRule` {#apiserver-config-k8s-io-v1-UserValidationRule}
- `UserValidationRule` {#apiserver-k8s-io-v1alpha1-UserValidationRule}
- `UserValidationRule` {#apiserver-k8s-io-v1beta1-UserValidationRule}
- `UtilizationShapePoint` {#kubescheduler-config-k8s-io-v1-UtilizationShapePoint}
- `ValidatingAdmissionPolicyStatusControllerConfiguration` {#kubecontrollermanager-config-k8s-io-v1alpha1-ValidatingAdmissionPolicyStatusControllerConfiguration}
- `VerbosityLevel` {#VerbosityLevel}
- `VModuleConfiguration` {#VModuleConfiguration}
- `VolumeBindingArgs` {#kubescheduler-config-k8s-io-v1-VolumeBindingArgs}
- `VolumeConfiguration` {#kubecontrollermanager-config-k8s-io-v1alpha1-VolumeConfiguration}
- `Waiting` {#container-state-waiting}
- `WatchPods` {#watch-pods}
- `WebhookAdmission` {#apiserver-config-k8s-io-v1-WebhookAdmission}
- `WebhookConfiguration` {#apiserver-config-k8s-io-v1-WebhookConfiguration}
- `WebhookConfiguration` {#apiserver-k8s-io-v1alpha1-WebhookConfiguration}
- `WebhookConfiguration` {#apiserver-k8s-io-v1beta1-WebhookConfiguration}
- `WebhookConfiguration` {#cloudcontrollermanager-config-k8s-io-v1alpha1-WebhookConfiguration}
- `WebhookConnectionInfo` {#apiserver-config-k8s-io-v1-WebhookConnectionInfo}
- `WebhookConnectionInfo` {#apiserver-k8s-io-v1alpha1-WebhookConnectionInfo}
- `WebhookConnectionInfo` {#apiserver-k8s-io-v1beta1-WebhookConnectionInfo}
- `WebhookMatchCondition` {#apiserver-config-k8s-io-v1-WebhookMatchCondition}
- `WebhookMatchCondition` {#apiserver-k8s-io-v1alpha1-WebhookMatchCondition}
- `WebhookMatchCondition` {#apiserver-k8s-io-v1beta1-WebhookMatchCondition}
- 0. Decide whether Pod Security Admission is right for you {#is-psa-right-for-you}
- 1. Configure the CRI implementation on nodes
- 1. Incoming traffic is evenly distributed
- 1. Review namespace permissions {#review-namespace-permissions}
- 2. Create the corresponding RuntimeClass resources
- 2. Simplify & standardize PodSecurityPolicies {#simplify-psps}
- 2. The Service has 3 or more endpoints per zone {#three-or-more-endpoints-per-zone}
- 2.a. Eliminate purely mutating fields {#eliminate-mutating-fields}
- 2.b. Eliminate options not covered by the Pod Security Standards {#eliminate-non-standard-options}
- 2.c. Rollout the updated PSPs {#psp-update-rollout}
- 3. Update Namespaces {#update-namespaces}
- 3.a. Identify an appropriate Pod Security level {#identify-appropriate-level}
- 3.b. Verify the Pod Security level {#verify-pss-level}
- 3.c. Enforce the Pod Security level {#enforce-pod-security-level}
- 3.d. Bypass PodSecurityPolicy {#bypass-psp}
- 4. Review namespace creation processes {#review-namespace-creation-process}
- 5. Disable PodSecurityPolicy {#disable-psp}
- A note on `--all-namespaces`
- A Note on Namespaces
- A quick note on service accounts
- A Simple Stateless Service
- A/AAAA records
- About CoreDNS
- About device allocation with DRA {#about-device-allocation-dra}
- About DRA {#about-dra}
- About the "Incompatible CNI versions" and "Failed to destroy network for sandbox" errors
- Access control
- Access control and permissions {#rbac-and-permissions}
- Access controls
- Access device metadata with a ResourceClaim {#access-metadata-resourceclaim}
- Access device metadata with a ResourceClaimTemplate {#access-metadata-template}
- Access Modes
- Access to `proxy` subresource of Nodes
- Access to key and certificate
- Accessing a custom resource
- Accessing ClusterTrustBundles from pods {#ctb-projection}
- Accessing for the first time with kubectl
- Accessing logs from Init Containers
- Accessing services running on the cluster
- Accessing the API from a Pod
- Accessing the API from within a Pod
- Accessing the Dashboard UI
- Accessing the Kubernetes API
- Accessing the MySQL instance
- Accessing the Service
- Achieving consensus
- active_file memory is not considered as available memory
- Add a label to a node
- Add a Secret generator
- Add ConfigMap data to a specific path in the Volume
- Add ConfigMap data to a Volume
- Add image pull secret to service account
- Add ImagePullSecrets to a service account
- Add labels to existing namespaces with `kubectl label`
- Add resource configs for MySQL and WordPress
- Adding a new ServiceCIDR
- Adding additional entries with hostAliases
- Adding custom plugin monitors
- Adding custom resources
- Adding kube-proxy parameters {#kube-proxy}
- Adding Linux worker nodes
- Adding more control plane nodes
- Adding support for other log format {#support-other-log-format}
- Adding Windows worker nodes
- Adding worker nodes {#join-nodes}
- Additional Considerations
- Additional information
- Additional information for kubeadm join
- Additional metadata in Pod bound tokens
- Additional Minikube setup instructions
- Additional printer columns
- Addon resources
- addonmanager.kubernetes.io/mode
- Addons
- Address types
- Addresses
- Adjust placeholder resource requests
- Admin access {#admin-access}
- Administration
- Admission control
- Admission control {#admission-control}
- Admission control extension points
- Admission control phases
- Admission controllers
- Admission webhook metrics
- AdmissionConfiguration
- Admonitions
- Adopt a multi-mode strategy
- Adopting built-in sidecar containers
- Advanced features and flexibility
- Advanced security hardening {#advanced}
- Advanced topics
- Advanced usage
- Advertise a new extended resource on one of your Nodes
- Affinity {#Affinity}
- Affinity and anti-affinity
- Aggregated ClusterRoles
- Aggregated discovery
- Aggregation layer
- AggregationRule {#AggregationRule}
- Algorithm details
- aliases
- All certificates
- AllocatedDeviceStatus {#AllocatedDeviceStatus}
- AllocationResult {#AllocationResult}
- Allow all egress traffic
- Allow all ingress traffic
- Allowed topologies
- Allowing additional audiences with RBAC {#allowing-additional-audiences}
- alpha.jobset.sigs.k8s.io/exclusive-topology
- alpha.jobset.sigs.k8s.io/namespaced-job
- alpha.jobset.sigs.k8s.io/no-schedule
- alpha.jobset.sigs.k8s.io/node-selector
- alpha.kubernetes.io/provided-node-ip (alpha) {#alpha-kubernetes-io-provided-node-ip}
- Alternate forms of the kubectl patch command
- Alternative Conversions
- Alternative: `kubectl apply -f <directory> --prune`
- Alternatives
- Alternatives to DaemonSet
- Alternatives to ReplicaSet
- Alternatives to ReplicationController
- Alternatives to Secrets
- AlwaysAdmit {#alwaysadmit}
- AlwaysDeny {#alwaysdeny}
- AlwaysPullImages {#alwayspullimages}
- An example containerd configuration file
- An example operator {#example}
- Annotations used for audit
- Anonymous authenticator configuration
- Anonymous requests
- Any Network Policy Ingress rules affecting the target Pods?
- apf.kubernetes.io/autoupdate-spec
- API
- API access extensions
- API access to authentication information for a client {#self-subject-review}
- API aggregation layer
- API Authentication
- API Authorization
- API changes
- API compatibility
- API compatibility {#api}
- API configuration: scheduling constraints
- API Definition {#api-definition}
- API discovery roles {#discovery-roles}
- API endpoints for health
- API Extension
- API extensions
- API groups
- API groups and versioning
- API implementation
- API kinds exempt from admission validation
- API kinds exempt from mutating admission
- API Object
- API objects {#api-overview}
- API Priority and Fairness
- API Reference
- API references {#reference}
- API server aggregation
- API server and load balancer
- API server identity
- API server to kubelet
- API server to nodes, pods, and services
- API structure
- API types for admission policies
- API verbs
- API versioning
- API-based signers {#signer-api}
- APIGroup {#APIGroup}
- APIGroupList {#APIGroupList}
- APIResource {#APIResource}
- APIResourceList {#APIResourceList}
- APIServer flags
- apiserver.latency.k8s.io/apf-queue-wait
- apiserver.latency.k8s.io/decode-response-object
- apiserver.latency.k8s.io/etcd
- APIService {#APIService}
- APIServiceCondition {#APIServiceCondition}
- APIServiceList {#APIServiceList}
- APIServiceSpec {#APIServiceSpec}
- APIServiceStatus {#APIServiceStatus}
- APIVersions {#APIVersions}
- app.kubernetes.io/component
- app.kubernetes.io/created-by (deprecated)
- app.kubernetes.io/instance
- app.kubernetes.io/managed-by
- app.kubernetes.io/name
- app.kubernetes.io/part-of
- app.kubernetes.io/version
- AppArmor
- AppArmor and SELinux: policy-based mandatory access control {#policy-based-mac}
- AppArmor profile within security context {#appArmorProfile}
- AppArmorProfile {#AppArmorProfile}
- Append $HOME/.kube/config to your KUBECONFIG environment variable
- appendArgs
- Appendix: Horizontal Pod Autoscaler Status Conditions
- Application design
- Application protocol
- Applications And Instances Of Applications
- Apply and Verify
- Apply policies using admission controllers
- Apply policies using API objects
- Apply policies using dynamic admission control
- Apply policies using Kubelet configurations
- Apply policies using ValidatingAdmissionPolicy
- Apply the kustomization file
- ApplyConfiguration {#ApplyConfiguration}
- Applying a Static Profile {#static-profile}
- Applying cluster configuration changes
- Applying CoreDNS configuration changes
- Applying Custom Profile {#custom-profile}
- Applying kube-proxy configuration changes
- Applying kubelet configuration changes
- Applying network policies
- Applying to a single namespace
- Applying to all namespaces
- applyset.kubernetes.io/additional-namespaces (alpha) {#applyset-kubernetes-io-additional-namespaces}
- applyset.kubernetes.io/contains-group-kinds (alpha) {#applyset-kubernetes-io-contains-group-kinds}
- applyset.kubernetes.io/contains-group-resources (deprecated) {#applyset-kubernetes-io-contains-group-resources}
- applyset.kubernetes.io/id (alpha) {#applyset-kubernetes-io-id}
- applyset.kubernetes.io/is-parent-type (alpha) {#applyset-kubernetes-io-is-parent-type}
- applyset.kubernetes.io/part-of (alpha) {#applyset-kubernetes-io-part-of}
- applyset.kubernetes.io/tooling (alpha) {#applyset-kubernetes-io-tooling}
- Approval
- Approval or rejection {#approval-rejection}
- Approval or rejection using `kubectl` {#approval-rejection-kubectl}
- Approval or rejection using the Kubernetes API {#approval-rejection-api-client}
- Approve the CertificateSigningRequest {#approve-certificate-signing-request}
- Approving CertificateSigningRequests {#approving-certificate-signing-requests}
- apps.kubernetes.io/pod-index (beta) {#apps-kubernetes.io-pod-index}
- Arbitrary workloads and arbitrary selectors {#arbitrary-controllers-and-selectors}
- Architecture Diagram
- Architecture variations
- Are DNS endpoints exposed?
- Are DNS queries being received/processed?
- Are the Pods working?
- Are you in the right namespace for the service?
- Assign a ServiceAccount to a Pod {#assign-to-pod}
- Assign an extended resource to a Pod
- Assign role to service accounts to use specific GMSA credspecs
- Assign SELinux labels to a Container
- Assign the policy to the service
- Associated lifetimes
- AttachedVolume {#AttachedVolume}
- Attaching metadata to objects
- Attempt to create a Pod that does not meet the minimum CPU request
- Attempt to create a Pod that does not meet the minimum memory request
- Attempt to create a Pod that exceeds the maximum CPU constraint
- Attempt to create a Pod that exceeds the maximum memory constraint
- Attempt to create a second PersistentVolumeClaim
- Attempt to create a second Pod
- Audit annotations
- Audit backends
- Audit policy
- audit.k8s.io/truncated
- AuditAnnotation {#AuditAnnotation}
- Auditing
- Authenticate API servers {#authenticate-apiservers}
- Authenticating proxy {#authenticating-proxy}
- Authenticating reverse proxy {#authenticating-proxy}
- Authenticating service account credentials {#authenticating-credentials}
- Authenticating service account credentials in your own code {#authenticating-in-code}
- Authenticating to network shares using hostname or FQDN
- Authentication
- Authentication & Authorization
- Authentication and authorization
- Authentication configuration {#api-server-authn-config}
- Authentication Flow
- Authentication methods
- Authentication strategies
- Authentication, authorization, and auditing
- Authoring Pods
- Authoring Profiles
- Authorization
- Authorization Algorithm
- Authorization and security considerations
- Authorization context
- Authorization mode configuration {#choice-of-authz-config}
- Authorization modes {#authorization-modules}
- Authorization verdicts {#determine-whether-a-request-is-allowed-or-denied}
- authorization.k8s.io/decision
- authorization.k8s.io/reason
- Authorize kubelet to create CSR
- Auto (deprecated) {#updateMode-Auto}
- Auto-generated legacy ServiceAccount token clean up {#auto-generated-legacy-serviceaccount-token-clean-up}
- Auto-provisioning {#autoprovisioning}
- Auto-reconciliation
- Automated preparation of component credentials by using kubeadm phases
- Automatic certificate renewal
- Automatic injection of sidecars
- Automatic labelling
- Automatic node labelling {#node-labeller}
- Automating kubeadm
- Autoscaler implementations
- Autoscalers {#autoscalers}
- Autoscaling based on cluster size
- Autoscaling based on schedules
- Autoscaling during rolling update
- Autoscaling on metrics not related to Kubernetes objects
- Autoscaling on more specific metrics
- Autoscaling on multiple metrics and custom metrics
- autoscaling.alpha.kubernetes.io/behavior (deprecated) {#autoscaling-alpha-kubernetes-io-behavior}
- Available fields
- Available providers {#providers}
- Avoid dependency loops {#avoid-dependency-loops}
- Avoid self-mutations {#avoid-self-mutation}
- Avoid sharing Secret manifests
- Avoid side effects {#avoid-side-effects}
- Avoiding collisions
- AWS EBS
- AWS EFS
- AWSElasticBlockStoreVolumeSource {#AWSElasticBlockStoreVolumeSource}
- Azure Disk
- Azure File (deprecated) {#azure-file}
- AzureDiskVolumeSource {#AzureDiskVolumeSource}
- AzureFilePersistentVolumeSource {#AzureFilePersistentVolumeSource}
- AzureFileVolumeSource {#AzureFileVolumeSource}
- Background
- Background cascading deletion {#background-deletion}
- Backing up an etcd cluster
- Backoff limit per index {#backoff-limit-per-index}
- Bare Pods
- Base Image for HostProcess Containers
- Base security hardening
- Baseline
- Bases and Overlays
- BASH
- Basic authentication Secret
- Basic policy
- Basic Structure
- BasicDevice {#BasicDevice}
- Basics
- BasicSchedulingPolicy {#BasicSchedulingPolicy}
- batch.kubernetes.io/controller-uid {#batchkubernetesio-controller-uid}
- batch.kubernetes.io/cronjob-scheduled-timestamp
- batch.kubernetes.io/job-completion-index
- batch.kubernetes.io/job-name {#batchkubernetesio-job-name}
- batch.kubernetes.io/job-tracking (deprecated) {#batch-kubernetes-io-job-tracking}
- Before you begin
- Behavior
- Behavior of `to` and `from` selectors
- Benefits of a built-in sidecar container
- Benefits of DRA {#dra-benefits}
- Best effort Pods scope {#quota-scope-best-effort}
- Best Practices
- Best practices and warnings
- BestEffort
- beta.kubernetes.io/arch (deprecated)
- beta.kubernetes.io/instance-type (deprecated)
- beta.kubernetes.io/os (deprecated)
- Bind
- Bind roles to explicit identities
- Bind verb
- Binding
- Binding {#Binding}
- Binding Block Volumes
- Bootstrap initialization
- Bootstrap Token Secret Format
- Bootstrap token Secrets
- Bootstrap tokens
- Bootstrap tokens {#bootstrap-tokens}
- Bootstrap Tokens Overview
- Bound service account token volume mechanism {#bound-service-account-token-volume}
- Bound service account tokens
- Break the Readiness probe
- Bugs and feature requests
- Built-in default constraints {#internal-default-constraints}
- Built-in Pod conditions {#built-in-pod-conditions}
- Built-in Pod Security admission enforcement
- Built-in PriorityClasses
- Built-in snapshot
- Bulk operations in kubectl
- Bullet lists
- Burstable
- CA Reusage and Conflicts
- Calculate the total reserved resources
- Call "kubeadm upgrade"
- Calling the Eviction API
- Canary Deployment
- Canary deployments
- Cannot use the metrics-server securely in a kubeadm cluster
- Capabilities {#Capabilities}
- Capacity
- Capacity and Allocatable {#capacity}
- CapacityRequestPolicy {#CapacityRequestPolicy}
- CapacityRequestPolicyRange {#CapacityRequestPolicyRange}
- CapacityRequirements {#CapacityRequirements}
- Capturing and analyzing Node/Pod traffic
- Capturing logs from workloads
- Cascading delete
- Cascading deletion {#cascading-deletion}
- Cassandra container environment variables
- Categories
- Caveats
- Caveats and limitations when preserving source IPs
- CBOR resource encoding {#cbor-encoding}
- CEL expressions
- CEL options, language features, and libraries
- CELDeviceSelector {#CELDeviceSelector}
- Ceph RBD (deprecated) {#ceph-rbd}
- CephFSPersistentVolumeSource {#CephFSPersistentVolumeSource}
- CephFSVolumeSource {#CephFSVolumeSource}
- Certificate Authority
- Certificate authority (CA) rotation {#certificate-authority-rotation}
- Certificate expiry and management {#check-certificate-expiration}
- Certificate management with kubeadm
- Certificate paths
- Certificate rotation
- Certificate signing authorization {#authorization}
- Certificate signing requests
- CertificateApproval {#certificateapproval}
- Certificates
- Certificates API
- CertificateSigning {#certificatesigning}
- CertificateSigningRequest {#CertificateSigningRequest}
- CertificateSigningRequestCondition {#CertificateSigningRequestCondition}
- CertificateSigningRequestList {#CertificateSigningRequestList}
- CertificateSigningRequestSpec {#CertificateSigningRequestSpec}
- CertificateSigningRequestStatus {#CertificateSigningRequestStatus}
- CertificateSubjectRestriction {#certificatesubjectrestriction}
- cfssl
- cgroup drivers
- cgroupfs driver {#cgroupfs-cgroup-driver}
- Chained selectors
- Chaining and filtering
- Change the parameter
- Changing built-in resources
- Changing management methods
- Changing the CPU Manager Policy
- Changing the default StorageClass
- Changing the owner from a configuration file to a direct imperative writer
- Changing the owner from a direct imperative writer to a configuration file
- Changing the package repository
- Changing the reclaim policy of a PersistentVolume
- Check application configuration
- Check control plane component manifests
- Check for 3rd party tooling and mutating webhooks
- Check for errors in the DNS pod
- Check if the DNS pod is running
- Check kubeconfig
- Check kubelet configuration
- Check mechanisms {#check-mechanisms}
- Check network adapters
- Check owner references on your pods
- Check required ports {#check-required-ports}
- Check the device plugin resource API {#device-plugin-resource-api}
- Check the local DNS configuration first
- Check the status of the minikube cluster
- Check the status of the PDB
- Check the subject represented by the kubeconfig
- Check via /flagz endpoint
- Check via metrics endpoint
- Check VPN connectivity
- Check your OS version
- Checking API access
- Checking DaemonSet `RollingUpdate` update strategy
- Checking for plugin warnings
- Checking Rollout History of a Deployment
- Checking the status of Init Containers
- Checklists
- Checkpoint file for device manager {#device-manager-state}
- Checkpoint files for resource managers {#resource-managers-state}
- Chicken and Egg
- Choice of resource
- Choose an admission control mechanism {#choose-admission-mechanism}
- Choose an approach
- Choose the right Pod Security Standard to apply
- Choosing a method for adding custom resources
- Choosing a user account
- Choosing an encryption algorithm {#choosing-encryption-algorithm}
- Choosing an update mechanism {#update-mechanism-choose}
- Choosing certificate validity period {#choosing-cert-validity-period}
- CinderPersistentVolumeSource {#CinderPersistentVolumeSource}
- CinderVolumeSource {#CinderVolumeSource}
- Claim resources {#claim-resources}
- Claim resources and deploy a Pod {#claim-resources-pod}
- Claims As Volumes
- Class
- Clean up
- Clean up {#clean-up}
- Clean up {#cleanup-1}
- Clean up {#cleanup-2}
- Clean up {#tear-down}
- Clean up finished jobs automatically
- Clean up Policy
- Clean up the control plane
- Cleanup {#cleanup-use-multiple-service-accounts}
- Cleanup for finished Jobs
- Cleanup of $HOME/.kube
- Cleanup of CNI configuration
- Cleanup of external etcd members
- Cleanup of network traffic rules
- Clearing `managedFields`
- CLI
- CLI access to authentication information {#self-subject-review-cli}
- Client and serving certificates
- Client certificates
- Client configuration
- Client extensions
- client-go credential plugins
- ClientIPConfig {#ClientIPConfig}
- Cloning existing data
- Cloud controller manager functions {#functions-of-the-ccm}
- Cloud native information security
- Cloud native security {#further-reading-cloud-native}
- Cloud provider resource quotas {#quota-issues}
- Cloud provider security
- cloud-controller-manager
- Cloud-native service discovery
- Cluster administrators
- Cluster defragmentation
- Cluster Diagram
- Cluster failure modes
- Cluster information
- Cluster Management
- Cluster management tools
- Cluster networking types {#cluster-network-ipfamilies}
- Cluster resilience {#resilience}
- Cluster trust bundles {#cluster-trust-bundles}
- cluster-autoscaler.kubernetes.io/enable-ds-eviction
- cluster-autoscaler.kubernetes.io/safe-to-evict
- Cluster-level default constraints
- Cluster-level Logging
- Cluster-level logging architectures
- ClusterRole {#ClusterRole}
- ClusterRoleBinding {#ClusterRoleBinding}
- ClusterRoleBindingList {#ClusterRoleBindingList}
- ClusterRoleList {#ClusterRoleList}
- ClusterTrustBundle {#ClusterTrustBundle}
- clusterTrustBundle projected volumes {#clustertrustbundle}
- ClusterTrustBundleList {#ClusterTrustBundleList}
- ClusterTrustBundleProjection {#ClusterTrustBundleProjection}
- ClusterTrustBundleSpec {#ClusterTrustBundleSpec}
- Code blocks
- Code blocks containing Hugo shortcodes
- Collections
- Combine workload and Node autoscaling
- Combining new APIs with automation
- Command Families
- Command line authorization mode configuration {#using-flags-for-your-authorization-module}
- Command line interface {#kubectl}
- Command line options for the kubelet {#kubelet-compatibility}
- Command line proxy
- Command-line utilities
- Common Features
- Common observability tools
- Common properties and validation {#ctb-common}
- Common tasks after bootstrapping control plane
- Common usage patterns
- Communicating with Daemon Pods
- Community-maintained client libraries
- Comparing ease of use
- Comparison with `service.kubernetes.io/topology-mode: Auto`
- Comparison with Client-Side Apply
- Comparison with Linux {#compatibility-linux-similarities}
- Comparison with podAffinity and podAntiAffinity {#comparison-with-podaffinity-podantiaffinity}
- Compatibility across topology changes
- Compatibility and limitations {#limitations}
- Compatibility matrix
- Complete deletion of a StatefulSet
- Complete Deployment
- Completion mode
- Component config structures
- Component configuration
- Component metrics
- Component traces
- ComponentCondition {#ComponentCondition}
- Components
- ComponentStatus {#ComponentStatus}
- ComponentStatusList {#ComponentStatusList}
- Composing and Customizing Resources
- Concepts
- Conclusion
- Concurrency policy
- Condition {#Condition}
- Conditions
- Conditions {#condition}
- Config API for kubeadm
- Config APIs
- config.kubernetes.io/local-config
- configMap
- ConfigMap {#ConfigMap}
- ConfigMap object
- ConfigMap Signing
- ConfigMapEnvSource {#ConfigMapEnvSource}
- ConfigMapKeySelector {#ConfigMapKeySelector}
- ConfigMapList {#ConfigMapList}
- ConfigMapNodeConfigSource {#ConfigMapNodeConfigSource}
- ConfigMapProjection {#ConfigMapProjection}
- ConfigMaps and Pods
- ConfigMapVolumeSource {#ConfigMapVolumeSource}
- Configurable container restart delay
- Configurable scaling behavior
- Configuration
- Configuration fields {#configure-probes}
- Configuration File Format
- Configuration for peer API server connectivity
- Configuration of Stub-domain and upstream nameserver using CoreDNS
- Configuration types
- Configuration via command line arguments {#api-server-authn-config-cli}
- Configuration via configuration file {#api-server-authn-config-file}
- Configurations for local ephemeral storage {#configurations}
- Configurations to avoid {#reserved-memory-configurations-to-avoid}
- Configure a kubelet credential provider
- Configure a Pod
- Configure a projected volume for a pod
- Configure a volume for a Pod
- Configure access to external Secrets
- Configure admission webhooks on the fly
- Configure all cluster namespaces
- Configure all key-value pairs in a ConfigMap as container environment variables
- Configure all key-value pairs in a Secret as container environment variables
- Configure automatic reloading
- Configure certificates for user accounts
- Configure certificates manually
- Configure cluster role to enable RBAC on specific GMSA credential specs
- Configure CustomResourceDefinition to use conversion webhooks
- Configure encryption at rest
- Configure fine-grained SupplementalGroups control for a Pod {#supplementalgroupspolicy}
- Configure GMSA credential spec reference in Pod spec
- Configure GMSAs and Windows nodes in Active Directory
- Configure IPv4/IPv6 dual-stack
- Configure kubelets using kubeadm
- Configure kuberc
- Configure least-privilege access to Secrets
- Configure least-privilege access to Secrets {#least-privilege-secrets}
- Configure multiple feature gates
- Configure the Admission Controller
- Configure the API server to decrypt objects
- Configure the certificate into kubeconfig
- Configure the Konnectivity service
- Configure the kubelet to use containerd as its container runtime
- Configure TLS-Bootstrapping for node joining
- Configure volume permission and ownership change policy for Pods
- Configuring a cgroup driver
- Configuring a non-privileged user
- Configuring a ValidatingWebhookConfiguration from disk
- Configuring constrained impersonation with RBAC
- Configuring container user
- Configuring CPU management policies
- Configuring CRI
- Configuring garbage collection {#configuring-gc}
- Configuring graceful node shutdown
- Configuring kube-proxy
- Configuring kubelet
- Configuring logging
- Configuring manifest-based admission control {#configuration}
- Configuring memory reservation
- Configuring network
- Configuring nodes to authenticate to a private registry
- Configuring Pod overhead {#set-up}
- Configuring Pod schedulingGates
- Configuring rolling update strategy
- Configuring the API Server using an authorization config file {#using-configuration-file-for-authorization}
- Configuring the container runtime cgroup driver
- Configuring the KMS provider
- Configuring the Kubelet
- Configuring the kubelet cgroup driver
- Configuring your cluster to provide signing
- Confirm your DRA driver exposes a liveness probe and utilize it
- Conflicts
- Conformance
- Connecting your local machine to a remote Kubernetes cluster
- Considerations {#considerations}
- Considerations about apiserver-advertise-address and ControlPlaneEndpoint
- Considerations for downgrade and rollback
- Considerations for managing custom configurations {#considerations-custom-configurations}
- Considerations for memory backed `emptyDir` volumes {#memory-backed-emptydir}
- Considerations for using traffic distribution control
- Considerations when upgrading etcd
- Consistency
- Constants and well-known values and paths
- Constrained Impersonation
- Constraints
- Constraints on NUMA memory reservation
- Constraints on resource limits and requests
- Consumable capacity
- Consuming extended resources
- Contacting the webhook
- Container {#Container}
- Container environment
- Container garbage collection {#container-image-garbage-collection}
- Container hooks
- Container image lifecycle
- Container image pull Secrets {#using-imagepullsecrets}
- Container images
- Container information
- Container log streams
- Container networking on Windows {#networking}
- Container probes
- Container resize policies
- Container Resize Policy and Pod-Level Resize
- Container resource metrics
- Container resource monitoring
- Container resources example {#example-1}
- Container restarts {#restart-policy}
- Container runtime
- Container runtime integration
- Container runtime socket {#runtime-socket}
- Container runtimes
- Container runtimes {#container-runtime}
- Container states
- Container users
- Container-level `securityContext` recommendations {#security-context-container}
- Container-level security context {#container-level-security-context}
- container.apparmor.security.beta.kubernetes.io/* (deprecated) {#container-apparmor-security-beta-kubernetes-io}
- container.seccomp.security.alpha.kubernetes.io/[NAME] (non-functional) {#container-seccomp-security-alpha-kubernetes-io}
- containerd
- Containerd v1.6
- Containerd v1.7 (and greater)
- ContainerExtendedResourceRequest {#ContainerExtendedResourceRequest}
- ContainerImage {#ContainerImage}
- ContainerPort {#ContainerPort}
- ContainerResizePolicy {#ContainerResizePolicy}
- ContainerResourceMetricSource {#ContainerResourceMetricSource}
- ContainerResourceMetricStatus {#ContainerResourceMetricStatus}
- ContainerRestartRule {#ContainerRestartRule}
- ContainerRestartRuleOnExitCodes {#ContainerRestartRuleOnExitCodes}
- ContainerState {#ContainerState}
- ContainerStateRunning {#ContainerStateRunning}
- ContainerStateTerminated {#ContainerStateTerminated}
- ContainerStateWaiting {#ContainerStateWaiting}
- ContainerUser {#ContainerUser}
- Context
- Contextual Logging
- Contributing causes
- Control admission webhooks
- Control plane
- Control plane automated approval {#approval-rejection-control-plane}
- Control plane behavior
- Control plane components
- Control plane deployment options
- Control plane details
- Control plane isolation
- Control plane node isolation
- Control Plane nodes
- Control plane protection
- Control plane signer {#signer-control-plane}
- Control plane to node
- Control via API server
- control-plane.alpha.kubernetes.io/leader (deprecated) {#control-plane-alpha-kubernetes-io-leader}
- controlledValues
- Controller pattern
- Controller-managed and user-managed PodGroups
- controller-uid (deprecated) {#controller-uid}
- controller.kubernetes.io/pod-deletion-cost {#pod-deletion-cost}
- ControllerManager flags
- ControllerRevision {#ControllerRevision}
- ControllerRevisionList {#ControllerRevisionList}
- Controlling access to the Kubelet
- Controlling access to the Kubernetes API
- Controlling the capabilities of a workload or user at runtime
- Controlling what privileges containers run with
- Controlling which nodes pods may access
- Convert your secret data to a base-64 representation
- Converting the volume mode of a Snapshot {#convert-volume-mode}
- Copying a Pod while adding a new container
- Copying a Pod while changing container images
- Copying a Pod while changing its command
- Copying files and directories to and from containers
- Copying the administrator certificate (optional) {#admin-certificate-copy}
- Core component roles
- Core Components
- Core design principles
- CoreDNS
- CoreDNS ConfigMap options
- Counter {#Counter}
- CounterSet {#CounterSet}
- CPU
- CPU management {#resource-management-cpu}
- CPU manager
- CPU resource units {#meaning-of-cpu}
- CPU units
- Create a Certificate Authority
- Create a certificate signing request
- Create a CertificateSigningRequest object to send to the Kubernetes API
- Create a ConfigMap
- Create a ConfigMap {#configmap}
- Create a ConfigMap from generator
- Create a ConfigMap using `kubectl create configmap`
- Create a container image
- Create a container image {#create-an-image}
- Create a CustomResourceDefinition
- Create a DaemonSet
- Create a Deployment
- Create a dual-stack cluster
- Create a dual-stack load balanced Service
- Create a Kubernetes CertificateSigningRequest {#create-k8s-certificatessigningrequest}
- Create a kustomization.yaml
- Create a LimitRange and a Pod
- Create a local Kubernetes cluster with kind
- Create a minikube cluster
- Create a MutatingAdmissionPolicy
- Create a namespace
- Create a new nginx.conf file
- Create a PersistentVolume
- Create a PersistentVolumeClaim
- Create a PersistentVolumeClaim from a Volume Snapshot {#create-persistent-volume-claim-from-volume-snapshot}
- Create a Pod
- Create a Pod that does not specify any CPU request or limit
- Create a Pod that does not specify any memory request or limit
- Create a Pod that gets assigned a QoS class of BestEffort
- Create a Pod that gets assigned a QoS class of Burstable
- Create a Pod that gets assigned a QoS class of Guaranteed
- Create a pod that gets scheduled to specific node
- Create a pod that gets scheduled to your chosen node
- Create a Pod that has access to the secret data through a Volume
- Create a Pod that has an Init Container
- Create a Pod that has two Containers
- Create a Pod that uses the container runtime default seccomp profile
- Create a Pod that uses your Secret
- Create a Pod with a seccomp profile for syscall auditing
- Create a Pod with a seccomp profile that causes violation
- Create a Pod with a seccomp profile that only allows necessary syscalls
- Create a pod with CPU requests and limits at pod-level
- Create a pod with memory requests and limits at pod-level
- Create a pod with resource requests and limits at both pod-level and container-level
- Create a PriorityClass
- Create a ResourceQuota
- Create a second configuration file
- Create a Secret
- Create a Secret based on existing credentials {#registry-secret-existing-credentials}
- Create a Secret by providing credentials on the command line
- Create a Secret directly with kubectl
- Create a Service
- Create a Service from a manifest
- Create a Service using kubectl
- Create a simple Pod to use as a test environment
- Create a single-stack cluster
- Create a static pod {#static-pod-creation}
- Create a swap file and turn swap on
- Create additional API tokens {#create-token}
- Create an `nginx` deployment and expose it via a service
- Create an index.html file on your Node
- Create an ip-masq-agent
- Create an X.509 certificate signing request {#create-x.509-certificatessigningrequest}
- Create certificate signing requests (CSR)
- Create cluster
- Create custom objects
- Create DeviceClasses {#create-deviceclasses}
- Create GMSA credential spec resources
- Create Jobs based on a template
- Create Jobs from the manifests
- Create load balancer for kube-apiserver
- Create manifests from the template
- Create new namespaces
- Create PersistentVolumeClaim from an existing PVC {#create-persistent-volume-claim-from-an-existing-pvc}
- Create PersistentVolumeClaims and PersistentVolumes
- Create pods in each namespace
- Create private key
- Create Role and RoleBinding
- Create Services {#services}
- Create the config file
- Create the HorizontalPodAutoscaler {#create-horizontal-pod-autoscaler}
- Create the kustomization file
- Create the PDB object
- Create the placeholder deployment
- Create the Pod that references that ResourceClaim
- Create the ResourceClaim
- Create the Secret {#create-the-config-file}
- Create the StatefulSet {#statefulset}
- Creating a Calico cluster with Google Kubernetes Engine (GKE)
- Creating a CronJob {#creating-a-cron-job}
- Creating a DaemonSet with `RollingUpdate` update strategy
- Creating a delegated cgroup tree
- Creating a Deployment
- Creating a headless Service for Cassandra {#creating-a-cassandra-headless-service}
- Creating a local Calico cluster with kubeadm
- Creating a new namespace
- Creating a Pod that runs two Containers
- Creating a PodGroup
- Creating a Secret
- Creating a Secret with a Docker config
- Creating a Service
- Creating a service for an application running in five pods
- Creating a service for an application running in two pods
- Creating a StatefulSet
- Creating a user namespace
- Creating a ValidatingAdmissionPolicy
- Creating a ZooKeeper ensemble
- Creating and editing an object from a URL without saving the configuration
- Creating and exploring an nginx deployment
- Creating MongoDB deployment and service
- Creating objects
- Creating the `hello` Service object
- Creating the autoscaler declaratively
- Creating the backend using a Deployment
- Creating the frontend
- Creating the Frontend Service
- Creating the Guestbook Frontend Deployment
- Creating the Redis Deployment
- Creating the Redis follower service
- Creating the Redis leader Service
- Creation ordering
- Credential plugin policy
- credentialPluginAllowlist
- credentialPluginPolicy
- CRI Configuration
- CRI Pod & Container Metrics
- CRI version support {#cri-versions}
- CRI-O
- crictl
- CronJob {#CronJob}
- CronJob behavior
- CronJob limitations {#cron-job-limitations}
- cronjob.kubernetes.io/instantiate {#cronjob-kubernetes-io-instantiate}
- CronJobList {#CronJobList}
- CronJobSpec {#CronJobSpec}
- CronJobStatus {#CronJobStatus}
- Cross namespace data sources
- Cross-namespace pod affinity scope
- Cross-platform support
- CrossVersionObjectReference {#CrossVersionObjectReference}
- csi
- CSI driver restrictions
- CSI ephemeral volumes
- CSI volume attach limits and cluster autoscaler
- CSIDriver {#CSIDriver}
- CSIDriverList {#CSIDriverList}
- CSIDriverSpec {#CSIDriverSpec}
- CSINode {#CSINode}
- CSINodeDriver {#CSINodeDriver}
- CSINodeList {#CSINodeList}
- CSINodeSpec {#CSINodeSpec}
- CSIPersistentVolumeSource {#CSIPersistentVolumeSource}
- CSIStorageCapacity {#CSIStorageCapacity}
- CSIStorageCapacityList {#CSIStorageCapacityList}
- CSIVolumeSource {#CSIVolumeSource}
- CSRs and certificate issuing
- Custom controllers
- Custom heuristics
- Custom resource definitions
- Custom resource field selectors
- Custom resources
- Custom resources and Server-Side Apply
- Custom resources fields
- Custom signers
- Customization and extensibility
- Customizing CoreDNS
- Customizing kube-proxy
- Customizing plugin weights and bin-packing resource weights
- Customizing the control plane with flags in `ClusterConfiguration`
- Customizing the kubelet {#kubelet}
- Customizing the termination message
- Customizing with patches {#patches}
- CustomResourceColumnDefinition {#CustomResourceColumnDefinition}
- CustomResourceConversion {#CustomResourceConversion}
- CustomResourceDefinition {#CustomResourceDefinition}
- CustomResourceDefinitionCondition {#CustomResourceDefinitionCondition}
- CustomResourceDefinitionList {#CustomResourceDefinitionList}
- CustomResourceDefinitionNames {#CustomResourceDefinitionNames}
- CustomResourceDefinitions
- CustomResourceDefinitionSpec {#CustomResourceDefinitionSpec}
- CustomResourceDefinitionStatus {#CustomResourceDefinitionStatus}
- CustomResourceDefinitionVersion {#CustomResourceDefinitionVersion}
- CustomResourceSubresources {#CustomResourceSubresources}
- CustomResourceSubresourceScale {#CustomResourceSubresourceScale}
- CustomResourceSubresourceStatus {#CustomResourceSubresourceStatus}
- CustomResourceValidation {#CustomResourceValidation}
- DaemonEndpoint {#DaemonEndpoint}
- DaemonSet
- DaemonSet {#DaemonSet}
- DaemonSet rolling update is stuck
- DaemonSet Update Strategy
- DaemonSetCondition {#DaemonSetCondition}
- DaemonSetList {#DaemonSetList}
- DaemonSets and node-pressure eviction {#daemonset}
- DaemonSetSpec {#DaemonSetSpec}
- DaemonSetStatus {#DaemonSetStatus}
- DaemonSetUpdateStrategy {#DaemonSetUpdateStrategy}
- Dashboard
- Data Plane Isolation
- Data source references
- Deadline for delayed Job start {#starting-deadline}
- Dealing with disruptions
- Debug endpoints
- Debug logging
- Debugging a Node using `kubectl debug node`
- Debugging a Pod or Node while applying a profile {#debugging-profiles}
- Debugging a StatefulSet
- Debugging Hook handlers
- Debugging Pods
- Debugging Replication Controllers
- Debugging Services
- Debugging using a copy of the Pod
- Debugging via a shell on the node {#node-shell-session}
- Debugging with an ephemeral debug container {#ephemeral-container}
- Debugging with container exec {#container-exec}
- Debugging Workloads
- Declarative APIs
- Declarative Application Management
- Declarative object configuration
- Declarative scaling using `kubectl apply`
- Declarative validation tag reference
- Declarative vs imperative
- Declared features {#declaredfeatures}
- Decode the Secret {#decoding-secret}
- Decrypt all data {#decrypting-all-data}
- Default behavior
- Default Configuration
- Default deny all egress traffic
- Default deny all ingress and all egress traffic
- Default deny all ingress traffic
- Default field values
- Default hosts file content
- Default IngressClass {#default-ingress-class}
- Default NIC When using flannel as the pod network in Vagrant
- Default Pod hostname
- Default policies
- Default roles and role bindings
- Default service accounts {#default-service-accounts}
- Default StorageClass
- Default threshold
- DefaultBackend {#default-backend}
- Defaulting
- Defaulting Behavior
- DefaultIngressClass {#defaultingressclass}
- Defaults
- DefaultStorageClass {#defaultstorageclass}
- DefaultTolerationSeconds {#defaulttolerationseconds}
- Define a command and arguments when you create a Pod
- Define a container environment variable with data from a single ConfigMap
- Define a container environment variable with data from a single Secret
- Define a gRPC liveness probe
- Define a Kubernetes Deployment for the scheduler
- Define a liveness command
- Define a liveness HTTP request
- Define a TCP liveness probe
- Define access label and test again
- Define an environment dependent variable for a container
- Define an environment variable for a container
- Define an Indexed Job
- Define clusters, users, and contexts
- Define container environment variables using ConfigMap data
- Define container environment variables using Secret data
- Define container environment variables with data from multiple ConfigMaps
- Define container environment variables with data from multiple Secrets
- Define postStart and preStop handlers
- Define readiness probes
- Define the DaemonSet
- Defining a Job
- Defining a PriorityClass
- Defining a Service
- Defining controller selectors and PodTemplate labels
- Defining custom stop signals
- Delayed creation of replacement pods {#pod-replacement-policy}
- Delegating volume permission and ownership change to CSI driver
- Delegation of managing a Job object to external controller
- Delete
- Delete a CustomResourceDefinition
- Delete a Pod that has a claim {#delete-pod-claim}
- Delete owner objects and orphan dependents {#set-orphan-deletion-policy}
- Delete Pods
- Delete the Pod
- Delete/invalidate a long-lived/legacy ServiceAccount token {#delete-legacy-token}
- Delete/invalidate a ServiceAccount token {#delete-token}
- Delete/invalidate a short-lived ServiceAccount token {#delete-short-lived}
- DeleteOptions {#DeleteOptions}
- Deleting a CronJob {#deleting-a-cron-job}
- Deleting a deployment
- Deleting a namespace
- Deleting a ReplicaSet and its Pods
- Deleting a ReplicationController and its Pods
- Deleting a ServiceCIDR
- Deleting a StatefulSet
- Deleting just a ReplicaSet
- Deleting only a ReplicationController
- Deleting resources
- Deleting StatefulSets
- Deletion protection
- DeletionPolicy
- DenyServiceExternalIPs
- Dependency on Docker explained {#role-of-dockershim}
- Deploy an app
- Deploy Cloud Controller Manager
- Deploy MySQL
- Deploy the admission webhook service
- Deploy the conversion webhook service
- Deploy the DRA driver components
- Deploying Antrea with kubeadm
- Deploying Cilium for Production Use
- Deploying Cilium on Minikube for Basic Testing
- Deploying containerized applications
- Deploying operators
- Deploying the Dashboard UI
- Deploying the KMS plugin
- Deploying your first app on Kubernetes
- Deployment (recommended)
- Deployment {#Deployment}
- Deployment and Scaling Guarantees
- Deployment status
- Deployment tools
- deployment.kubernetes.io/desired-replicas
- deployment.kubernetes.io/max-replicas
- deployment.kubernetes.io/revision
- deployment.kubernetes.io/revision-history
- DeploymentCondition {#DeploymentCondition}
- DeploymentList {#DeploymentList}
- Deployments
- DeploymentSpec {#DeploymentSpec}
- DeploymentStatus {#DeploymentStatus}
- Deprecated annotation
- Deprecated kubelet garbage collection features
- Deprecating a feature or behavior
- Deprecating a flag or CLI
- Deprecating a metric
- Deprecating parts of the API
- Deprecation
- Deprecation of cgroup v1
- Descheduler
- Describing a Kubernetes object
- Descriptions for removed feature gates
- Design
- Design admission webhooks for low latency {#design-admission-webhooks-low-latency}
- Design Docs
- Design principles
- Desired versus current state {#desired-vs-current}
- Detailed behavior
- Detecting a stalled rollout
- Detecting Docker dependency from node agents
- Detecting server support
- Detection of kubelet restarts
- Determine whether DNS horizontal autoscaling is already enabled {#determining-whether-dns-horizontal-autoscaling-is-already-enabled}
- Determine whether encryption at rest is already enabled
- Determine whether encryption at rest is already enabled {#determining-whether-encryption-at-rest-is-already-enabled}
- Determine which version to upgrade to
- Developers
- Developing
- Developing a KMS plugin gRPC server
- Developing or debugging an existing service
- Device {#Device}
- Device binding conditions
- Device Health Monitoring {#device-health-monitoring}
- Device manager
- Device plugin and unhealthy devices
- Device plugin deployment
- Device plugin examples {#examples}
- Device plugin implementation
- Device plugin integration with the Topology Manager
- Device plugin registration
- Device Plugins
- Device taints and tolerations
- Device taints and tolerations {#device-taints-and-tolerations}
- DeviceAllocationConfiguration {#DeviceAllocationConfiguration}
- DeviceAllocationResult {#DeviceAllocationResult}
- DeviceAttribute {#DeviceAttribute}
- DeviceCapacity {#DeviceCapacity}
- DeviceClaim {#DeviceClaim}
- DeviceClaimConfiguration {#DeviceClaimConfiguration}
- DeviceClass {#deviceclass}
- DeviceClassConfiguration {#DeviceClassConfiguration}
- DeviceClassList {#DeviceClassList}
- DeviceClassSpec {#DeviceClassSpec}
- DeviceConstraint {#DeviceConstraint}
- DeviceCounterConsumption {#DeviceCounterConsumption}
- DeviceRequest {#DeviceRequest}
- DeviceRequestAllocationResult {#DeviceRequestAllocationResult}
- DeviceSelector {#DeviceSelector}
- DeviceSubRequest {#DeviceSubRequest}
- DeviceTaint {#DeviceTaint}
- DeviceTaintRule {#DeviceTaintRule}
- DeviceTaintRuleList {#DeviceTaintRuleList}
- DeviceTaintRuleSpec {#DeviceTaintRuleSpec}
- DeviceTaintRuleStatus {#DeviceTaintRuleStatus}
- DeviceTaintSelector {#DeviceTaintSelector}
- DeviceToleration {#DeviceToleration}
- Diagnosing the problem
- Diagnostics
- Differences from application containers
- Differences from init containers
- Differences from regular containers
- Differences from sidecar containers
- Direct control
- Direct Server Return (DSR) {#dsr}
- Directly accessing the REST API
- Disable DNS horizontal autoscaling
- Disable kuberc
- Disable swap for system-critical daemons
- Disabling DeclarativeValidationBeta {#opt-out}
- Disabling metrics
- Disabling native histograms
- Disallow labeling nodes
- Discovering builtin services
- Discovering plugins
- Discovering services
- Discovering what cluster CA to trust
- Discovery API
- Discovery cluster-info
- Discussion
- Disruption mode types
- DisruptionTarget {#disruption-target}
- Disruptive updates
- Distributing kubectl plugins
- Distributing nodes across zones
- Distributing Self-Signed CA Certificate
- Distribution of EndpointSlices
- DNS
- DNS Records
- DNS resolution on Windows nodes {#dns-windows}
- DNS search domain list limits
- DNS Subdomain Names
- docker attach
- Docker Compose Versions
- Docker config Secrets
- Docker Engine {#docker}
- docker exec
- docker info
- docker login
- docker logs
- docker ps
- docker run
- docker stop and docker rm
- docker version
- Does any Service work by DNS name? {#does-any-service-exist-in-dns}
- Does CoreDNS have sufficient permissions?
- Does the Service exist?
- Does the Service have any EndpointSlices?
- Does the Service work by DNS name?
- Does the Service work by IP?
- Don't change immutable objects {#dont-change-immutable-objects}
- Don't overwrite array values {#dont-overwrite-arrays}
- Don't rely on mutating webhook invocation order {#dont-rely-webhook-order}
- Downgrading from server-side apply to client-side apply
- Download and set up the kubelet
- Download example seccomp profiles {#download-profiles}
- Download the certificate and use it
- Download, install, and configure the components
- downwardAPI {#downwardapi}
- DownwardAPIProjection {#DownwardAPIProjection}
- DownwardAPIVolumeFile {#DownwardAPIVolumeFile}
- DownwardAPIVolumeSource {#DownwardAPIVolumeSource}
- DRA alpha features {#alpha-features}
- DRA beta features {#beta-features}
- DRA device metadata in containers {#device-metadata}
- DRA driver deployment and maintenance
- DRA kubeletplugin operations
- DRA terminology {#terminology}
- DRA, CSI, and Device plugins
- Drain a Node
- Drain the node
- Draining multiple nodes in parallel
- Driver
- Drop-in directory for kubelet configuration files {#kubelet-conf-d}
- Dry-run
- Dry-run authorization
- Dual-stack Service configuration scenarios
- Duplicate endpoints
- During cluster initialization
- Dynamic addition and removal of static pods
- Dynamic admission control
- Dynamic volume limits
- easyrsa
- Edge case: A Pod fails to reach itself via the Service IP {#a-pod-fails-to-reach-itself-via-the-service-ip}
- Edit a Secret {#edit-secret}
- Editing a Secret
- Editing resources
- Effect of Pod priority on scheduling order
- Efficient detection of changes
- Efficient SELinux volume relabeling
- Egress traffic
- Elastic Indexed Jobs
- Embedding certificates in kubeconfig files
- Embrace the principle of least privilege
- emptyDir {#emptydir}
- EmptyDirVolumeSource {#EmptyDirVolumeSource}
- Emulated Version
- Enable addons
- Enable audit logging
- Enable DNS horizontal autoscaling {#enablng-dns-horizontal-autoscaling}
- Enable IPv4 packet forwarding
- Enable IPv4 packet forwarding {#prerequisite-ipv4-forwarding-optional}
- Enable IPv6 packet forwarding {#prerequisite-ipv6-forwarding}
- Enable kubectl autocompletion
- Enable Kubernetes Apiserver flags
- Enable leader election
- Enable Pod Security Standards checking for that namespace
- Enable shell autocompletion
- Enable the use of `RuntimeDefault` as the default seccomp profile for all workloads
- Enabling AppArmor or SELinux
- Enabling bin packing using MostAllocated strategy
- Enabling bin packing using RequestedToCapacityRatio
- Enabling Bootstrap Token Authentication
- Enabling client certificate rotation
- Enabling coordinated leader election
- Enabling Dynamic Provisioning
- Enabling graceful node shutdown
- Enabling native histograms
- Enabling node declared features
- Enabling Node Problem Detector
- Enabling Opportunistic Batching
- Enabling or disabling API groups {#enabling-or-disabling}
- Enabling Peer-aggregated Discovery and Mixed Version Proxy
- Enabling QoS and Pod level cgroups
- Enabling Resource Quota
- Enabling Seccomp
- Enabling signed kubelet serving certificates {#kubelet-serving-certs}
- Enabling the KMS supported by your cloud provider
- Enabling Topology Aware Routing
- Enabling Unsafe Sysctls
- Enabling/Disabling API Priority and Fairness
- Encodings
- Encrypt secrets at rest
- Encrypt your data {#encrypting-your-data}
- Encrypting your data with the KMS provider
- Endpoint {#Endpoint}
- EndpointAddress {#EndpointAddress}
- EndpointConditions {#EndpointConditions}
- EndpointHints {#EndpointHints}
- EndpointPort {#EndpointPort}
- Endpoints (deprecated) {#endpoints}
- Endpoints {#Endpoints}
- endpoints.kubernetes.io/last-change-trigger-time (deprecated) {#endpoints-kubernetes-io-last-change-trigger-time}
- endpoints.kubernetes.io/managed-by (deprecated) {#endpoints-kubernetes-io-managed-by}
- endpoints.kubernetes.io/over-capacity (deprecated) {#endpoints-kubernetes-io-over-capacity}
- EndpointSlice {#EndpointSlice}
- EndpointSlice API {#endpointslice-resource}
- EndpointSlice controller {#implementation-control-plane}
- EndpointSlice mirroring
- endpointslice.kubernetes.io/managed-by {#endpointslicekubernetesiomanaged-by}
- endpointslice.kubernetes.io/skip-mirror {#endpointslicekubernetesioskip-mirror}
- EndpointSliceList {#EndpointSliceList}
- EndpointSlices
- EndpointsList {#EndpointsList}
- EndpointSubset {#EndpointSubset}
- Enforcement of minimum and maximum CPU constraints
- Enforcement of minimum and maximum memory constraints
- Enforcement through validation
- Enforcing a ValidatingAdmissionPolicy from disk
- Enforcing Node Allocatable
- Enhanced Pod readiness
- EnqueueExtension
- Ensure all relevant data are encrypted {#ensure-all-secrets-are-encrypted}
- Ensure image pull credential verification {#ensureimagepullcredentialverification}
- Ensure that mutations don't violate validations {#ensure-mutations-dont-violate-validations}
- Ensure that the mutating webhooks in your cluster are idempotent {#ensure-mutating-webhook-idempotent}
- Ensure the feature gate is enabled
- Ensuring all secrets are encrypted
- Ensuring consistent configuration
- Ensuring OS-specific workloads land on the appropriate container host
- Enumerated or constant values
- Env file syntax {#env-file-syntax}
- EnvFromSource {#EnvFromSource}
- Environment variables
- EnvVar {#EnvVar}
- EnvVarSource {#EnvVarSource}
- Ephemeral storage consumption management {#resource-emphemeralstorage-consumption}
- Ephemeral volumes managed by kubelet
- EphemeralContainer {#EphemeralContainer}
- EphemeralVolumeSource {#EphemeralVolumeSource}
- Escalate verb
- Escalation paths {#escalation-paths}
- Escaping
- Estimated cost limits
- etcd
- Etcd flags
- etcd pods restart continually
- etcd storage
- Evaluation order
- Event {#Event}
- Event batching {#batching}
- Event driven Autoscaling
- EventList {#EventList}
- EventRateLimit {#eventratelimit}
- EventSeries {#EventSeries}
- EventSource {#EventSource}
- Eviction {#Eviction}
- Eviction monitoring interval
- Eviction signals {#eviction-signals}
- Eviction signals and thresholds
- Eviction Thresholds
- Evictions
- ExactDeviceRequest {#ExactDeviceRequest}
- Examine system logs
- Examine the memory manager state on a node
- Examining pod logs {#examine-pod-logs}
- Examining the Pod's ordinal index
- Example
- Example {#credential-plugin-policy-example}
- Example {#example-pod}
- Example {#example-streaming-lists}
- Example {#ssa-example-configmap}
- Example 1 {#allocation-example-1}
- Example 1: Resizing CPU without restart
- Example 2 {#allocation-example-2}
- Example 2: Resizing memory with restart
- Example 3 {#allocation-example-3}
- Example application {#sidecar-example}
- Example Configuration
- Example configuration with a secret, a downwardAPI, and a configMap {#example-configuration-secret-downwardapi-configmap}
- Example configuration: secrets with a non-default permission mode set {#example-configuration-secrets-nondefault-permission-mode}
- Example crictl commands
- Example debugging using ephemeral containers {#ephemeral-container-example}
- Example flow with endpoint termination
- Example manifest (excerpt) {#manifest-example}
- Example Non-preempting PriorityClass
- Example plugin
- Example Pod {#runtimeclass-pod-example}
- Example PriorityClass
- Example RBAC patterns
- Example resource constraints
- Example Scenario
- Example Scenarios
- Example use case
- Example Use Cases
- Example: alerting based on from kube-state-metrics {#example-kube-state-metrics-alert-1}
- Example: change downscale stabilization window
- Example: conflicting topology spread constraints {#example-conflicting-topologyspreadconstraints}
- Example: debugging a down/unreachable node
- Example: debugging Pending Pods
- Example: disable scale down
- Example: limit scale down rate
- Example: multiple topology spread constraints {#example-multiple-topologyspreadconstraints}
- Example: one topology spread constraint {#example-one-topologyspreadconstraint}
- Example: Provide prod/test credentials to Pods using Secrets {#provide-prod-test-creds}
- Example: Resizing Pod-Level Resources
- Example: topology spread constraints with node affinity {#example-topologyspreadconstraints-with-nodeaffinity}
- Example: using metrics from kube-state-metrics to query the cluster state {#example-kube-state-metrics-query-1}
- Examples
- Examples {#allocation-examples}
- Examples {#examples}
- Examples of good implementations {#example-good-implementations}
- Examples: Common operations
- Examples: Creating and using plugins
- Exceed a Container's memory limit
- Exceptions
- ExecAction {#ExecAction}
- Execute a command in a running container
- Executing commands on the container
- Execution time tweaks for watch requests
- Exempt requests
- Exemptions
- ExemptPriorityLevelConfiguration {#ExemptPriorityLevelConfiguration}
- Existing resources aren't affected {#limitation-admission-policy-validation}
- Expanding Persistent Volumes Claims
- experimental.windows.kubernetes.io/isolation-type (deprecated) {#experimental-windows-kubernetes-io-isolation-type}
- Experimenting with admission webhooks
- Explicitly Reserved CPU List
- Explore the $HOME/.kube directory
- Explore the DRA state
- Explore the initial cluster state {#explore-initial-state}
- Exploring the Kubernetes API
- Exporter
- Exposing logs directly from the application
- Exposing pods to the cluster
- Exposing the Service
- ExpressionWarning {#ExpressionWarning}
- Extend Service IP Ranges
- Extend the number of available IPs for Services
- Extended resource allocation by DRA {#extended-resource}
- Extended resources
- ExtendedResourceToleration {#extendedresourcetoleration}
- Extending kubectl with plugins
- Extension Apiserver Authenticates the Request
- Extension Apiserver Authorizes the Request
- Extension Apiserver Executes
- Extension patterns
- Extension points
- Extensions
- External APIs
- External CA mode {#external-ca-mode}
- External etcd nodes
- External etcd topology
- External integrations
- External IPs
- External load balancer providers
- External ServiceAccount token signing and key management
- External sources {#third-party}
- External tools
- External traffic policy
- ExternalDocumentation {#ExternalDocumentation}
- ExternalMetricSource {#ExternalMetricSource}
- ExternalMetricStatus {#ExternalMetricStatus}
- Facilitating leader election
- Fail open and validate the final state {#fail-open-validate-final-state}
- Failed Deployment
- Failed to destroy network for sandbox error
- Failing across availability zones
- Failure Policy
- failure-domain.beta.kubernetes.io/region (deprecated) {#failure-domainbetakubernetesioregion}
- failure-domain.beta.kubernetes.io/zone (deprecated) {#failure-domainbetakubernetesiozone}
- FAQ
- Fault recovery
- fc (fibre channel) {#fc}
- FCVolumeSource {#FCVolumeSource}
- Feature gates for Alpha or Beta features
- Feature gates for graduated or deprecated features
- Feature gates in Kubernetes v{{% skew currentVersion %}} {#list-of-gates}
- Feature gates that are removed
- Feature stages
- feature.node.kubernetes.io/*
- Feedback {#feedback}
- FetchKeys
- Field management
- Field managers {#managers}
- Field pruning
- Field selection {#field-selection}
- Field selectors
- Field validation
- Fields of REST resources
- FieldSelectorAttributes {#FieldSelectorAttributes}
- FieldSelectorRequirement {#FieldSelectorRequirement}
- FieldsV1 {#FieldsV1}
- File references
- File watching and dynamic reloading {#dynamic-reloading}
- FileKeySelector {#FileKeySelector}
- Filesystem support
- Filesystem-hosted static Pod manifest {#configuration-files}
- Fill the queue with tasks
- Filling the queue with tasks
- Filter
- Filter for specific requests by using match conditions {#filter-match-conditions}
- Finalizers
- Find out information about the kubelet and the Pod {#find-out-information}
- Find out the container runtime used on a Node
- Find out what container runtime endpoint you use {#which-endpoint}
- Finding if your app has a dependencies on Docker {#find-docker-dependencies}
- Finding your IP address
- Fine-grained authorization
- First steps for both methods
- FISH
- flagz
- Flannel troubleshooting
- Flexibility in Architecture
- FlexPersistentVolumeSource {#FlexPersistentVolumeSource}
- flexVolume (deprecated) {#flexvolume}
- FlexVolumeSource {#FlexVolumeSource}
- FlockerVolumeSource {#FlockerVolumeSource}
- FlowDistinguisherMethod {#FlowDistinguisherMethod}
- FlowSchema
- FlowSchema {#FlowSchema}
- FlowSchemaCondition {#FlowSchemaCondition}
- FlowSchemaList {#FlowSchemaList}
- FlowSchemaSpec {#FlowSchemaSpec}
- FlowSchemaStatus {#FlowSchemaStatus}
- For app developers
- For application developers
- For cluster administrators
- Force decryption
- Force Deletion
- Force deletion of StatefulSet pods
- Forced Pod termination {#pod-termination-forced}
- Forced rollback
- Forced storage detach on timeout {#storage-force-detach-on-timeout}
- Foreground cascading deletion {#foreground-deletion}
- Formatting output
- ForNode {#ForNode}
- Forum
- Forward a local port to a port on the Pod
- ForZone {#ForZone}
- Framework workflow
- Full metrics pipeline
- Functions in Kubernetes JSONPath {#functions}
- Further investigation
- Further reading
- Future work
- Gang policy
- Gang scheduling with Jobs
- GangSchedulingPolicy {#GangSchedulingPolicy}
- Garbage collecting load balancers
- Garbage collection of Pods {#pod-garbage-collection}
- Garbage collection of unused containers and images {#containers-images}
- Gateway {#api-kind-gateway}
- gateway.networking.k8s.io/generator
- GatewayClass {#api-kind-gateway-class}
- gcePersistentDisk (deprecated) {#gcepersistentdisk}
- GCEPersistentDiskVolumeSource {#GCEPersistentDiskVolumeSource}
- General good practice
- General Guidelines
- General usage
- Generate CSRs
- Generate kubeconfig files for control plane components
- Generate static Pod manifest for local etcd
- Generate static Pod manifests for control plane components
- Generate the encryption key {#generate-key-no-kms}
- Generate the necessary certificates
- Generated values
- Generating configuration
- Generating CPU Pressure
- Generating I/O Pressure
- Generating kubeconfig files for additional users {#kubeconfig-additional-users}
- Generating Memory Pressure
- Generating Resources
- Generic ephemeral volumes
- Get a container's logs
- Get the certificate
- Get the CertificateSigningRequest approved {#get-the-certificate-signing-request-approved}
- Get the name of your DNS Deployment {#find-scaling-target}
- Get the names of your Nodes
- Getting a shell to a container
- Getting details about Init Containers
- Getting help
- Getting help and troubleshooting {#troubleshooting}
- Getting started with KYAML
- Getting Started with MutatingAdmissionPolicies
- Getting Started with Validating Admission Policy
- Getting Started: Deploying a Windows workload
- gitRepo (disabled) {#gitrepo}
- GitRepoVolumeSource {#GitRepoVolumeSource}
- Glossary
- GlusterfsPersistentVolumeSource {#GlusterfsPersistentVolumeSource}
- GlusterfsVolumeSource {#GlusterfsVolumeSource}
- Go applications
- Go client
- Good practice for pod readiness {#pod-readiness-good-practices}
- Good practice for using swap in a Kubernetes cluster
- Good practices {#node-pressure-eviction-good-practices}
- Good practices for using API Priority and Fairness
- Good practices for using swap memory
- Graceful kube-apiserver shutdown
- Graceful node shutdown
- Graceful node shutdown {#graceful-node-shutdown}
- Grant access to Migration Lease
- Grant least-privilege permissions for synthetic subresources
- Grant multi-node controller permissions only when needed
- Grant node-local driver permissions
- Grant permissions to a ServiceAccount {#grant-permissions}
- Grant scheduler and allocation-controller permissions
- Granular status authorization {#granular-status-authorization}
- GroupResource {#GroupResource}
- GroupSubject {#GroupSubject}
- GroupVersionForDiscovery {#GroupVersionForDiscovery}
- gRPC probes {#grpc-probes}
- GRPCAction {#GRPCAction}
- GRPCRoute {#api-kind-grpcroute}
- Guaranteed
- H3
- Handling kubelet restarts
- Handling multiple Windows versions in the same cluster
- Handling Pod and container failures
- Handling process failure
- Harden DRA status update permissions
- Hardening
- Hardware recommendations and considerations {#windows-hardware-recommendations}
- Header within a tab list
- Heading levels
- Headlamp
- Headless Services
- Headless Services without selector
- Health check concurrency exemption
- Healthiness of a Pod
- Heartbeats
- Helm
- Help! My question isn't covered! I need help now!
- High availability considerations {#ha-considerations}
- Higher priority Pods are preempted before lower priority pods
- Historical context for Kubernetes {#going-back-in-time}
- Hook delivery guarantees
- Hook handler execution
- Hook handler implementations
- Horizontal workload autoscaling {#horizontal-workload-autoscaling}
- HorizontalPodAutoscaler {#HorizontalPodAutoscaler}
- HorizontalPodAutoscalerBehavior {#HorizontalPodAutoscalerBehavior}
- HorizontalPodAutoscalerCondition {#HorizontalPodAutoscalerCondition}
- HorizontalPodAutoscalerList {#HorizontalPodAutoscalerList}
- HorizontalPodAutoscalerSpec {#HorizontalPodAutoscalerSpec}
- HorizontalPodAutoscalerStatus {#HorizontalPodAutoscalerStatus}
- HostAlias {#HostAlias}
- HostIP {#HostIP}
- Hostname wildcards
- Hostname with pod's hostname and subdomain fields
- Hostname with pod's hostnameOverride
- Hostname with pod's setHostnameAsFQDN fields
- hostPath {#hostpath}
- HostPathVolumeSource {#HostPathVolumeSource}
- HostProcess Pod configuration requirements
- How a ReplicaSet works
- How a ReplicationController works
- How API-initiated eviction works
- How apply calculates differences and merges changes
- How can you avoid Service ClusterIP conflicts? {#avoid-ClusterIP-conflict}
- How certificates are used by your cluster
- How Daemon Pods are scheduled
- How different types of fields are merged
- How do I turn off an admission controller?
- How do I turn on an admission controller?
- How does a HorizontalPodAutoscaler work?
- How does a VerticalPodAutoscaler work?
- How does it work?
- How does Telepresence work?
- How does the Memory Manager operate?
- How finalizers work
- How is the swap limit being determined with LimitedSwap?
- How it fits together
- How it works
- How it works under the hood
- How kubectl works
- How kubelet retries Deferred resizes
- How Kubernetes applies resource requests and limits {#how-pods-with-resource-limits-are-run}
- How Kubernetes ResourceQuotas work
- How nodes handle container logs
- How pod-level resource managers work
- How Pods handle problems with containers {#container-restarts}
- How Pods with ephemeral-storage requests are scheduled
- How Pods with resource requests are scheduled
- How resource allocation with DRA works {#how-it-works}
- How Service ClusterIPs are allocated?
- How StatefulSets track changes using ControllerRevisions
- How storage versions are relevant to encryption at rest
- How the design works
- How the scheduler iterates over Nodes
- How the tool works
- How to apply/view/delete objects using Kustomize
- How to change ownership of a field between the configuration file and direct imperative writers
- How to clear server-defaulted fields or fields set by other writers
- How to create objects
- How to delete objects
- How to enable Feature Gates
- How to implement the Kubernetes network model
- How to install
- How to perform Disruptive Actions on your Cluster
- How to update objects
- How to use priority and preemption
- How to use service accounts {#how-to-use}
- How to view an object
- How topology manager works
- How volumes work
- HPAScalingPolicy {#HPAScalingPolicy}
- HPAScalingRules {#HPAScalingRules}
- HTTP {#protocol-http-special}
- HTTP access to authentication information {#self-subject-review-http-api}
- HTTP media types {#alternate-representations-of-resources}
- HTTP probes {#http-probes}
- HTTPGetAction {#HTTPGetAction}
- HTTPHeader {#HTTPHeader}
- HTTPIngressPath {#HTTPIngressPath}
- HTTPIngressRuleValue {#HTTPIngressRuleValue}
- HTTPRoute {#api-kind-httproute}
- Huge pages
- ID count for each of Pods
- Identify an Application to Protect
- Identify DaemonSets that depend on Docker Engine {#identify-docker-dependency}
- Identify devices to claim {#identify-devices}
- Identify DRA components that write status
- Identify the cgroup version on Linux Nodes {#check-cgroup-version}
- Identify whether you use admission webhooks {#identify-admission-webhooks}
- Identify which components need the feature gate
- If you do not specify a CPU limit
- If you do not specify a memory limit
- If you specify a CPU limit but do not specify a CPU request
- Illustrative Reconfiguration Steps
- image
- Image names
- Image pull per runtime class
- Image pull policy
- Image Pull Records
- Image security
- ImagePolicyWebhook {#imagepolicywebhook}
- ImagePullBackOff
- Images
- ImageVolumeSource {#ImageVolumeSource}
- ImageVolumeStatus {#ImageVolumeStatus}
- Immutable ConfigMaps {#configmap-immutable}
- Immutable Secrets {#secret-immutable}
- Impact of a container runtime restart
- Impact of a kubelet restart
- Impact of a node reboot
- Imperative commands
- Imperative object configuration
- Impersonate verb
- Impersonation modes
- Implementations
- Implementations {#implementations-admission-control}
- Implementations {#implementations-supplementalgroupspolicy}
- Implementing a KMS plugin
- Implicit conventions
- Implicit group memberships defined in `/etc/group` in the container image
- Implicit maintenance-mode deactivation
- Importance of good webhook design {#why-good-webhook-design-matters}
- Improve etcd management policies
- In tree
- In-cluster authentication and namespace overrides
- In-place Pod resize {#pod-resize-inplace}
- In-place updates of resources
- Includes
- Incompatible CNI versions error
- Increase the load {#increase-load}
- Individual health checks
- Influencing Pod scheduling decisions {#scheduling}
- Info
- Information available via `fieldRef` {#downwardapi-fieldRef}
- Information available via `resourceFieldRef` {#downwardapi-resourceFieldRef}
- Information security for Secrets
- Infrastructure
- Infrastructure extensions
- Ingress {#Ingress}
- Ingress backed by a single Service {#single-service-ingress}
- Ingress class
- Ingress controllers
- Ingress rules
- IngressBackend {#IngressBackend}
- IngressClass {#IngressClass}
- IngressClass scope
- ingressclass.kubernetes.io/is-default-class
- IngressClassList {#IngressClassList}
- IngressClassParametersReference {#IngressClassParametersReference}
- IngressClassSpec {#IngressClassSpec}
- IngressList {#IngressList}
- IngressLoadBalancerIngress {#IngressLoadBalancerIngress}
- IngressLoadBalancerStatus {#IngressLoadBalancerStatus}
- IngressPortStatus {#IngressPortStatus}
- IngressRule {#IngressRule}
- IngressServiceBackend {#IngressServiceBackend}
- IngressSpec {#IngressSpec}
- IngressStatus {#IngressStatus}
- IngressTLS {#IngressTLS}
- Init containers and Linux cgroups {#cgroups}
- Init scripts
- Init workflow {#init-workflow}
- Initial {#updateMode-Initial}
- Initial bootstrap authentication
- Initial Leader Migration configuration
- Initial namespaces
- Initialization process
- Initializing your control-plane node
- Inline elements
- Inline text styles
- InPlace {#updateMode-InPlace}
- InPlaceOrRecreate {#updateMode-InPlaceOrRecreate}
- Input and output formats
- insecure-sha1.invalid-cert.kubernetes.io/$hostname
- Inspecting the Secret `regcred`
- Install `kubectl convert` plugin
- Install a container runtime {#container-runtime}
- Install a swap-enabled cluster with kubeadm
- Install addons
- Install an example DRA driver {#install-example-driver}
- Install and configure prerequisites
- Install and enable a mutating webhook {#install-enable-mutating-webhook}
- Install bash-completion
- Install Containerd
- Install device drivers {#install-drivers}
- Install Kompose
- Install kubeadm and kubelet
- Install kubectl binary on Windows (via direct download or curl)
- Install kubectl binary with curl on Linux
- Install kubectl binary with curl on macOS
- Install kubectl for Windows (optional) {#install-kubectl}
- Install kubectl on Linux
- Install kubectl on macOS
- Install kubectl on Windows
- Install network plugins
- Install on Windows using Chocolatey, Scoop, or winget {#install-nonstandard-package-tools}
- Install the GMSACredentialSpec CRD
- Install the Weave Net addon
- Install using native package management
- Install using other package management
- Install webhooks to validate GMSA users
- Install with Homebrew on macOS
- Install with Macports on macOS
- Install workers
- Installation
- Installing a container runtime {#installing-runtime}
- Installing a Pod network add-on {#pod-network}
- Installing CoreDNS
- Installing crictl
- Installing Kube-router addon
- Installing kubeadm, kubelet and kubectl
- Installing kubectl
- Installing kubectl plugins
- Installing Plugins on Nodes
- Installing Romana with kubeadm
- Instructions
- Instrumentation
- Integrate with Workload APIs
- Integrating a KMS plugin with the remote KMS
- Integration with Pod security admission checks
- Inter-pod affinity and anti-affinity
- Interact with the frontend Service
- Interacting with Deployments and Services
- Interacting with Nodes and cluster
- Interacting with running Pods
- Interaction with Traffic Policies
- Interactions between Pod priority and quality of service {#interactions-of-pod-priority-and-qos}
- Interfaces
- Interim cleanup
- Internal traffic policy
- internal.config.kubernetes.io/* (reserved prefix) {#internal.config.kubernetes.io-reserved-wildcard}
- internal.config.kubernetes.io/index
- internal.config.kubernetes.io/path
- Interpretation of config.json {#config-json}
- IntOrString
- Introduction
- IP address allocation tracking
- IP address assignment to Services
- IP address management (IPAM) {#ipam}
- IP address ranges for Service virtual IP addresses {#service-ip-static-sub-range}
- IP Masquerade Agent User Guide
- IPAddress {#IPAddress}
- IPAddressList {#IPAddressList}
- IPAddressSpec {#IPAddressSpec}
- IPBlock {#IPBlock}
- IPVS proxy mode {#proxy-mode-ipvs}
- Is DNS service up?
- Is kube-proxy proxying?
- Is kube-proxy running?
- Is the kube-proxy working?
- Is the Service defined correctly?
- Is there a recommended set of admission controllers to use?
- iscsi
- ISCSIPersistentVolumeSource {#ISCSIPersistentVolumeSource}
- ISCSIVolumeSource {#ISCSIVolumeSource}
- Isolating Pods from a ReplicaSet
- Isolating pods from a ReplicationController
- Isolation
- Issue a certificate
- Job
- Job {#Job}
- Job creation
- Job Labels
- Job patterns
- Job template
- Job termination and cleanup
- Job tracking with finalizers
- job-name (deprecated) {#job-name}
- JobCondition {#JobCondition}
- JobList {#JobList}
- Jobs history limits
- Jobs with sidecar containers
- jobset.sigs.k8s.io/coordinator
- jobset.sigs.k8s.io/job-index
- jobset.sigs.k8s.io/job-key
- jobset.sigs.k8s.io/jobset-name
- jobset.sigs.k8s.io/replicatedjob-name
- jobset.sigs.k8s.io/replicatedjob-replicas
- JobSpec {#JobSpec}
- JobStatus {#JobStatus}
- JobTemplateSpec {#JobTemplateSpec}
- Join a node to dual-stack cluster
- JSON {#JSON}
- JSON log format
- JSON resource encoding {#json-encoding}
- JSON Web Token authentication
- JSONPatch {#JSONPatch}
- JSONSchemaProps {#JSONSchemaProps}
- JSONSchemaPropsOrArray {#JSONSchemaPropsOrArray}
- JSONSchemaPropsOrBool {#JSONSchemaPropsOrBool}
- K3s
- k8s.io/deprecated
- k8s.io/removed-release
- Katacoda Embedded Live Environment
- Kernel-level security features and privileged containers {#kernel-security-features-privileged-containers}
- Key behaviors for pod readiness {#pod-readiness-key-behaviors}
- Key considerations
- Key storage
- Key Terms
- KeyToPath {#KeyToPath}
- kind
- Klog
- Klog output
- KMS encryption and per-object encryption keys
- KMS v1
- KMS v1 {#configuring-the-kms-provider-kms-v1}
- KMS v1 {#encrypting-your-data-with-the-kms-provider-kms-v1}
- KMS v2
- KMS v2 {#configuring-the-kms-provider-kms-v2}
- KMS v2 {#encrypting-your-data-with-the-kms-provider-kms-v2}
- Known issues
- Known limitations
- Kompose
- Konnectivity service
- Krew {#distributing-krew}
- Kube controller manager lock release on exit
- kube proxy `nftables` proxy mode
- Kube Reserved
- kube-aggregator.kubernetes.io/automanaged {#kube-aggregator-kubernetesio-automanaged}
- kube-apiserver
- kube-apiserver configuration
- kube-apiserver traces
- kube-controller-manager
- kube-controller-manager configuration
- kube-proxy (optional) {#kube-proxy}
- kube-proxy {#implementation-kube-proxy}
- kube-proxy scheduled before node is initialized by cloud-controller-manager
- kube-scheduler
- kube-scheduler configuration
- kube-scheduler-simulator.sigs.k8s.io/bind-result
- kube-scheduler-simulator.sigs.k8s.io/filter-result
- kube-scheduler-simulator.sigs.k8s.io/finalscore-result
- kube-scheduler-simulator.sigs.k8s.io/permit-result
- kube-scheduler-simulator.sigs.k8s.io/permit-result-timeout
- kube-scheduler-simulator.sigs.k8s.io/postfilter-result
- kube-scheduler-simulator.sigs.k8s.io/prebind-result
- kube-scheduler-simulator.sigs.k8s.io/prefilter-result
- kube-scheduler-simulator.sigs.k8s.io/prefilter-result-status
- kube-scheduler-simulator.sigs.k8s.io/prescore-result
- kube-scheduler-simulator.sigs.k8s.io/reserve-result
- kube-scheduler-simulator.sigs.k8s.io/result-history
- kube-scheduler-simulator.sigs.k8s.io/score-result
- kube-scheduler-simulator.sigs.k8s.io/selected-node
- kubeadm
- kubeadm {#upgrade-kubeadm}
- kubeadm blocks waiting for control plane during installation
- kubeadm blocks when removing managed containers
- kubeadm certs {#cmd-certs}
- kubeadm certs certificate-key {#cmd-certs-certificate-key}
- kubeadm certs check-expiration {#cmd-certs-check-expiration}
- kubeadm certs generate-csr {#cmd-certs-generate-csr}
- kubeadm certs renew {#cmd-certs-renew}
- kubeadm config images list {#cmd-config-images-list}
- kubeadm config images pull {#cmd-config-images-pull}
- kubeadm config migrate {#cmd-config-migrate}
- kubeadm config print {#cmd-config-print}
- kubeadm config print init-defaults {#cmd-config-print-init-defaults}
- kubeadm config print join-defaults {#cmd-config-print-join-defaults}
- kubeadm config validate {#cmd-config-validate}
- kubeadm init phase addon {#cmd-phase-addon}
- kubeadm init phase bootstrap-token {#cmd-phase-bootstrap-token}
- kubeadm init phase certs {#cmd-phase-certs}
- kubeadm init phase control-plane {#cmd-phase-control-plane}
- kubeadm init phase etcd {#cmd-phase-etcd}
- kubeadm init phase kubeconfig {#cmd-phase-kubeconfig}
- kubeadm init phase kubelet-finalize {#cmd-phase-kubelet-finalize-all}
- kubeadm init phase kubelet-start {#cmd-phase-kubelet-start}
- kubeadm init phase mark-control-plane {#cmd-phase-mark-control-plane}
- kubeadm init phase preflight {#cmd-phase-preflight}
- kubeadm init phase show-join-command {#cmd-phase-show-join-command}
- kubeadm init phase upload-certs {#cmd-phase-upload-certs}
- kubeadm init phase upload-config {#cmd-phase-upload-config}
- kubeadm init phase wait-control-plane {#cmd-phase-wait-control-plane}
- kubeadm init workflow internal design
- kubeadm join phase {#cmd-join-phase}
- kubeadm join phase control-plane-join {#cmd-join-phase-control-plane-join}
- kubeadm join phase control-plane-prepare {#cmd-join-phase-control-plane-prepare}
- kubeadm join phase etcd-join {#cmd-join-phase-etcd-join}
- kubeadm join phase kubelet-start {#cmd-join-phase-kubelet-start}
- kubeadm join phase preflight {#cmd-join-phase-preflight}
- kubeadm join phase wait-control-plane {#cmd-join-wait-control-plane}
- kubeadm join phases internal design
- kubeadm kubeconfig {#cmd-kubeconfig}
- kubeadm kubeconfig user {#cmd-kubeconfig-user}
- kubeadm node initialization
- kubeadm reset phase {#cmd-reset-phase}
- kubeadm reset phase cleanup-node {#cmd-reset-phase-cleanup-node}
- kubeadm reset phase preflight {#cmd-reset-phase-preflight}
- kubeadm reset phase remove-etcd-member {#cmd-reset-phase-remove-etcd-member}
- kubeadm reset workflow internal design
- kubeadm token create {#cmd-token-create}
- kubeadm token delete {#cmd-token-delete}
- kubeadm token generate {#cmd-token-generate}
- kubeadm token list {#cmd-token-list}
- kubeadm upgrade apply
- kubeadm upgrade apply {#cmd-upgrade-apply}
- kubeadm upgrade apply phase {#cmd-apply-phase}
- kubeadm upgrade diff
- kubeadm upgrade diff {#cmd-upgrade-diff}
- kubeadm upgrade guidance
- kubeadm upgrade node
- kubeadm upgrade node {#cmd-upgrade-node}
- kubeadm upgrade node phase {#cmd-node-phase}
- kubeadm upgrade plan
- kubeadm upgrade plan {#cmd-upgrade-plan}
- kubeadm upgrade workflow internal design
- kubeadm.alpha.kubernetes.io/cri-socket (deprecated) {#kubeadm-alpha-kubernetes-io-cri-socket}
- kubeadm.kubernetes.io/component-config.hash
- kubeadm.kubernetes.io/etcd.advertise-client-urls
- kubeadm.kubernetes.io/kube-apiserver.advertise-address.endpoint
- kubeadm's skew against kubeadm
- kubeadm's skew against the kubelet
- kubeadm's skew against the Kubernetes version
- kubectl
- kubectl apply
- kubectl apply: kube-apiserver — Runs authentication, authorization (RBAC) and admission control
- kubectl apply: kube-controller-manager/scheduler — Reconcile controllers act on the new object
- kubectl apply: kubectl — Reads manifest (YAML/JSON) from file/stdin
- kubectl apply: kubelet — Node kubelet schedules and starts containers via container runtime
- kubectl approval
- Kubectl autocomplete
- kubectl basics
- Kubectl context and configuration
- kubectl edit
- Kubectl output verbosity and debugging
- kubectl patch
- kubectl.kubernetes.io/default-container
- kubectl.kubernetes.io/default-logs-container (deprecated)
- kubectl.kubernetes.io/last-applied-configuration
- kubectl.kubernetes.io/restartedAt {#kubectl-k8s-io-restart-at}
- kubelet
- Kubelet authentication
- Kubelet authorization
- Kubelet client certificate rotation fails {#kubelet-client-cert}
- kubelet configuration
- Kubelet configuration files
- Kubelet configuration merging order
- Kubelet configuration patterns
- Kubelet credential provider for authenticated image pulls {#kubelet-credential-provider}
- kubelet device metrics {#monitoring-resources}
- Kubelet image credential provider plugins
- kubelet may not observe memory pressure right away
- kubelet Pressure Stall Information (PSI) metrics
- kubelet traces
- Kubelet's server and client certificates
- Kubelets outside the `system:nodes` group
- Kubelets with undifferentiated usernames
- Kubernetes `kompose convert` example
- Kubernetes and information security {#further-reading-k8s}
- Kubernetes API terminology {#standard-api-terminology}
- Kubernetes Apiserver Authentication and Authorization
- Kubernetes Apiserver Proxies the Request
- Kubernetes authorizer library
- Kubernetes Basics Modules
- Kubernetes binaries and package contents
- Kubernetes CEL libraries
- Kubernetes CIDR library
- Kubernetes Clusters
- Kubernetes default limits
- Kubernetes Default ServiceCIDR Reconfiguration
- Kubernetes Deployments
- Kubernetes format library
- Kubernetes IP address library
- Kubernetes IP address ranges
- Kubernetes list library
- Kubernetes Pods
- Kubernetes project
- Kubernetes Protobuf encoding {#protobuf-encoding}
- Kubernetes quantity library
- Kubernetes RBAC - denial of service risks {#denial-of-service-risks}
- Kubernetes RBAC - privilege escalation risks {#privilege-escalation-risks}
- Kubernetes regex library
- Kubernetes security mechanisms {#security-mechanisms}
- Kubernetes semver library
- Kubernetes Service CIDR Policies
- Kubernetes ServiceCIDR Reconfiguration Categories
- Kubernetes signers
- Kubernetes URL library
- kubernetes.io/arch
- kubernetes.io/change-cause {#change-cause}
- kubernetes.io/cluster-service (deprecated) {#kubernetes-io-cluster-service}
- kubernetes.io/config.hash
- kubernetes.io/config.mirror
- kubernetes.io/config.seen
- kubernetes.io/config.source
- kubernetes.io/description {#description}
- kubernetes.io/egress-bandwidth
- kubernetes.io/enforce-mountable-secrets (deprecated) {#enforce-mountable-secrets}
- kubernetes.io/hostname {#kubernetesiohostname}
- kubernetes.io/ingress-bandwidth
- kubernetes.io/ingress.class (deprecated)
- kubernetes.io/legacy-token-invalid-since
- kubernetes.io/legacy-token-last-used
- kubernetes.io/limit-ranger
- kubernetes.io/metadata.name
- kubernetes.io/os
- kubernetes.io/psp (deprecated) {#kubernetes-io-psp}
- kubernetes.io/service-account.name
- kubernetes.io/service-account.uid
- kubernetes.io/service-name {#kubernetesioservice-name}
- Kui
- Kustomize Feature List
- Label selector updates
- Label selectors
- Labels
- Labels on Jobs and Pods
- Labels on the ReplicationController
- Labels, annotations and taints used on API objects
- LabelSelector {#LabelSelector}
- LabelSelectorAttributes {#LabelSelectorAttributes}
- LabelSelectorRequirement {#LabelSelectorRequirement}
- Language overview
- Launch a Pod using service account token projection
- Leader election
- Leader selection for Kubernetes components
- Learning environment
- Lease {#Lease}
- LeaseCandidate {#LeaseCandidate}
- LeaseCandidateList {#LeaseCandidateList}
- LeaseCandidateSpec {#LeaseCandidateSpec}
- LeaseList {#LeaseList}
- LeaseSpec {#LeaseSpec}
- Least privilege
- Legacy Add-ons
- Legacy built-in kubelet credential provider
- Legacy ServiceAccount token cleaner
- Legacy ServiceAccount token tracking controller
- Leveraging `observedGeneration` Fields
- Lifecycle {#Lifecycle}
- Lifecycle and PersistentVolumeClaim
- Lifecycle of a volume and claim
- Lifecycle of a volume snapshot and volume snapshot content
- Lifecycle Pod conditions {#lifecycle-pod-conditions}
- LifecycleHandler {#LifecycleHandler}
- Limit access to the `nginx` service
- Limit edit access to mutating webhooks {#limit-edit-access}
- Limit the scope of each webhook {#webhook-limit-scope}
- Limitations
- Limitations {#limitations}
- Limitations and caveats
- Limitations for Alpha release {#workload-integration-limitations}
- Limitations of preemption
- LimitedPriorityLevelConfiguration {#LimitedPriorityLevelConfiguration}
- Limiting access of etcd clusters
- Limiting resource usage on a cluster
- LimitPodHardAntiAffinityTopology {#limitpodhardantiaffinitytopology}
- LimitRange {#LimitRange}
- LimitRange and admission checks for Pods
- LimitRange resources
- LimitRange to limit requests for storage
- LimitRangeItem {#LimitRangeItem}
- LimitRangeList {#LimitRangeList}
- LimitRanger {#limitranger}
- LimitRangeSpec {#LimitRangeSpec}
- LimitResponse {#LimitResponse}
- Links
- Linux
- Linux container security
- Linux Distribution cgroup v2 support
- Linux kernel long term maintenance
- LinuxContainerUser {#LinuxContainerUser}
- List all Container images in all namespaces
- LIST and WATCH filtering
- List Container images by Pod
- List Container images filtering by Pod label
- List Container images filtering by Pod namespace
- List Container images using a go-template instead of jsonpath
- List containers
- List images
- List of Alpha Kubernetes Metrics
- List of Beta Kubernetes Metrics
- List of feature gates {#feature-gates}
- List of Stable Kubernetes Metrics
- List of supported fields
- List pods
- List streaming {#list-streaming}
- List type attributes {#list-type-attributes}
- Listing all Sysctl Parameters
- Listing secrets
- Listing your cluster
- ListMeta {#ListMeta}
- Lists
- Liveness probe
- Liveness probe {#liveness-probe}
- Load Balancing
- Load balancing {#load-balancing}
- Load balancing and Services
- LoadBalancerIngress {#LoadBalancerIngress}
- LoadBalancerStatus {#LoadBalancerStatus}
- Local
- Local accounts {#local-accounts}
- Local ephemeral storage
- LocalObjectReference {#LocalObjectReference}
- LocalSubjectAccessReview {#LocalSubjectAccessReview}
- LocalVolumeSource {#LocalVolumeSource}
- Locate the encryption configuration file
- Locate use of deprecated APIs
- Locking
- Log backend
- Log entry truncation {#truncate}
- Log in to Docker Hub
- Log location
- Log locations {#log-location-node}
- Log query
- Log rotation
- Log verbosity level
- Logging tools
- Logs
- Logs and auditing
- Looking at logs
- Loopback CNI
- Maintaining etcd clusters
- Maintenance of the Mandatory and Suggested Configuration Objects
- Make a dry-run request
- Make in-place updates on your StatefulSets
- Making additional changes while paused
- Manage clusters with different types of GPUs
- Managed node labels
- ManagedFieldsEntry {#ManagedFieldsEntry}
- Management
- Management techniques
- Managing a cluster
- Managing access to the `/proc` filesystem {#proc-access}
- Managing credential plugin policy with `kubectl kuberc set`
- Managing extended resources
- Managing Revision History
- Managing rollouts
- Managing the kubeadm drop-in file for the kubelet {#kubelet-drop-in}
- Managing the ZooKeeper process
- Managing Workload Identity with Group Managed Service Accounts
- Mandatory Configuration Objects
- Manifests
- Manual certificate distribution {#manual-certs}
- Manual certificate renewal
- Manual deployments
- Manual Node administration
- Manual Operations for Replacing the Default ServiceCIDR
- Manual preparation of component credentials
- Manual Secret management for ServiceAccounts
- Manual zone assignment for Pods
- Manually create a long-lived API token for a ServiceAccount
- Manually create an API token for a ServiceAccount
- Manually deploy a node that runs the kubelet in a user namespace {#userns-the-hard-way}
- Maps, including Nested Structures
- Mark the node as control-plane
- Marking a Secret as immutable {#secret-immutable-create}
- Marking pod as critical
- Match all versions of an API {#match-all-versions}
- MatchCondition {#MatchCondition}
- Matching requests: `matchConditions`
- Matching requests: matchPolicy
- Matching requests: namespaceSelector
- Matching requests: objectSelector
- Matching requests: rules
- MatchResources {#MatchResources}
- Maximum parallel image pulls
- Maximum unavailable Pods
- Measuring resource usage
- Memory
- Memory management {#resource-management-memory}
- Memory manager
- Memory Manager configuration
- Memory manager reserved memory syntax {#reserved-memory-syntax}
- Memory QoS with cgroup v2
- Memory resource units {#meaning-of-memory}
- Memory throttling
- Memory units
- Memory-backed volumes
- Merge patch calculation
- Merge strategy
- Merging changes for fields of type list
- Merging changes to map fields
- Merging changes to primitive fields
- Merging kubeconfig files
- Message expression
- Metadata
- Metadata-only fetches
- Metric cardinality enforcement
- Metric lifecycle
- MetricIdentifier {#MetricIdentifier}
- Metrics
- Metrics (v1.36)
- Metrics and observability
- Metrics API
- Metrics in Kubernetes
- Metrics Server
- Metrics tools
- MetricSpec {#MetricSpec}
- MetricStatus {#MetricStatus}
- MetricTarget {#MetricTarget}
- MetricValueStatus {#MetricValueStatus}
- MicroTime {#MicroTime}
- Migrate to non-deprecated APIs
- Migrating dashboards and alerts
- Migrating Deployments and StatefulSets to horizontal autoscaling
- Migrating existing PersistentVolumes
- Migrating from imperative command management to declarative object configuration
- Migrating from imperative commands to imperative object configuration
- Migrating from imperative object configuration to declarative object configuration
- Migrating from Ingress
- Migrating to a different storage version
- Migrating to cgroup v2 {#migrating-cgroupv2}
- Migrating to CoreDNS
- Migrating to the `systemd` driver
- Migrating to the `systemd` driver in kubeadm managed clusters
- Migration between client-side and server-side apply
- Migration considerations
- Migration from dockershim
- Min Ready Seconds
- minikube
- Minimize distribution of privileged tokens
- Minimum eviction reclaim
- Minimum ready seconds
- Mirantis Container Runtime {#mcr}
- Mirror Pods {#mirror-pods}
- Missing PodGroup reference
- missing-san.invalid-cert.kubernetes.io/$hostname
- Mitigations
- Mitigations {#etcd-api-mitigations}
- Mitigations {#runtime-socket-mitigations}
- Mitigations {#static-pods-mitigations}
- Mixed version proxying
- Modify the kubelet ConfigMap
- Modifying a CronJob
- Modifying resources when they are created or changed {#mutation}
- Modifying the Cassandra StatefulSet
- ModifyVolumeStatus {#ModifyVolumeStatus}
- Monitor and tune components for higher load, especially in high scale environments
- Monitoring admission webhooks
- Monitoring compute & memory resource usage
- Monitoring device plugin resources
- Monitoring rollout progress
- More information
- Motivation
- Motivation for CPU requests and limits
- Motivation for default CPU limits and requests
- Motivation for default memory limits and requests
- Motivation for memory requests and limits
- Motivation for minimum and maximum CPU constraints
- Motivation for minimum and maximum memory constraints
- Mount options
- Mount propagation
- Mounted ConfigMaps are updated automatically
- Mounting the same PersistentVolume in two places
- Move the index.html file on your Node to a new folder
- Multi-architecture images with image indexes
- Multi-node etcd cluster
- Multi-node etcd cluster with load balancer
- Multi-node status controller permissions
- Multi-port Services
- Multiple customers
- Multiple profiles
- Multiple release tracks
- Multiple Replicas
- Multiple resource types
- Multiple teams
- Mutable CSI Node Allocatable Count
- Mutable Pod resources for suspended Jobs
- Mutable Pod scheduling directives
- Mutable Scheduling Directives
- Mutating webhook auditing annotations
- Mutating webhook deployment {#mutating-webhook-deployment}
- Mutating webhook ordering and idempotence {#ordering-idempotence}
- MutatingAdmissionPolicy {#MutatingAdmissionPolicy}
- MutatingAdmissionPolicyBinding {#MutatingAdmissionPolicyBinding}
- MutatingAdmissionPolicyBindingList {#MutatingAdmissionPolicyBindingList}
- MutatingAdmissionPolicyBindingSpec {#MutatingAdmissionPolicyBindingSpec}
- MutatingAdmissionPolicyList {#MutatingAdmissionPolicyList}
- MutatingAdmissionPolicySpec {#MutatingAdmissionPolicySpec}
- MutatingAdmissionWebhook {#mutatingadmissionwebhook}
- MutatingWebhook {#MutatingWebhook}
- MutatingWebhookConfiguration {#MutatingWebhookConfiguration}
- MutatingWebhookConfigurationList {#MutatingWebhookConfigurationList}
- Mutation {#Mutation}
- Mutation scope and field considerations {#mutation-scope-considerations}
- Mutation testing and validation {#mutation-testing-validation}
- My container is terminated
- My Pods are pending with event message `FailedScheduling`
- Name based virtual hosting
- NamedRuleWithOperations {#NamedRuleWithOperations}
- Names
- Namespace {#Namespace}
- Namespace modification
- Namespace per tenant
- NamespaceAutoProvision {#namespaceautoprovision}
- NamespaceCondition {#NamespaceCondition}
- NamespaceExists {#namespaceexists}
- NamespaceLifecycle {#namespacelifecycle}
- NamespaceList {#NamespaceList}
- Namespaces
- Namespaces and DNS
- Namespaces of Services
- NamespaceSpec {#NamespaceSpec}
- NamespaceStatus {#NamespaceStatus}
- Naming a plugin
- Naming convention {#naming}
- Native / platform specific package management {#distributing-native}
- Navigation
- Network configuration
- Network isolation
- Network modes
- Network Plugin Requirements
- Network plugins
- Network policies
- Network security
- Network traffic filtering
- Network troubleshooting {#troubleshooting-network}
- NetworkDeviceData {#NetworkDeviceData}
- Networking
- Networking and Network Policy
- Networking and security
- NetworkPolicy {#NetworkPolicy}
- NetworkPolicy and `hostNetwork` pods
- NetworkPolicy's impact on existing connections
- NetworkPolicyEgressRule {#NetworkPolicyEgressRule}
- NetworkPolicyIngressRule {#NetworkPolicyIngressRule}
- NetworkPolicyList {#NetworkPolicyList}
- NetworkPolicyPeer {#NetworkPolicyPeer}
- NetworkPolicyPort {#NetworkPolicyPort}
- NetworkPolicySpec {#NetworkPolicySpec}
- nfd.node.kubernetes.io/extended-resources
- nfd.node.kubernetes.io/feature-labels
- nfd.node.kubernetes.io/master.version
- nfd.node.kubernetes.io/node-name
- nfd.node.kubernetes.io/worker.version
- NFS
- NFSVolumeSource {#NFSVolumeSource}
- Node {#Node}
- Node affinity
- Node Allocatable
- Node allocatable resources {#node-allocatable-resources}
- Node and container level metric statistics
- Node behavior
- Node components
- Node condition oscillation
- Node conditions {#node-conditions}
- Node Conformance Test
- Node consolidation {#consolidation}
- Node constraints imposed by autoscaler configuration {#provisioning-node-constraints}
- Node controller
- Node controller {#authorization-node-controller}
- Node heartbeats
- Node heartbeats {#node-heart-beats}
- Node Isolation
- Node isolation/restriction
- Node labels
- Node labels {#built-in-node-labels}
- Node name uniqueness
- Node out of memory behavior
- Node PID limits
- Node Prerequisite
- Node problem detector
- Node provisioning {#provisioning}
- Node scoring for capacity allocation
- Node scoring threshold {#percentage-of-nodes-to-score}
- Node selection in kube-scheduler {#kube-scheduler-implementation}
- Node selectors
- Node status
- Node status fields
- Node to Control Plane
- Node topology
- Node-aware DRA verbs
- Node-level troubleshooting {#troubleshooting-node}
- Node-local DRA driver permissions
- node-role.kubernetes.io/*
- node-role.kubernetes.io/control-plane
- node-role.kubernetes.io/control-plane {#node-role-kubernetes-io-control-plane-taint}
- node-role.kubernetes.io/master (deprecated) {#node-role-kubernetes-io-master-taint}
- node.alpha.kubernetes.io/ttl (deprecated)
- node.cloudprovider.kubernetes.io/shutdown
- node.cloudprovider.kubernetes.io/uninitialized
- node.kubernetes.io/disk-pressure
- node.kubernetes.io/exclude-from-external-load-balancers
- node.kubernetes.io/instance-type {#nodekubernetesioinstance-type}
- node.kubernetes.io/memory-pressure
- node.kubernetes.io/network-unavailable
- node.kubernetes.io/not-ready
- node.kubernetes.io/out-of-service
- node.kubernetes.io/pid-pressure
- node.kubernetes.io/unreachable
- node.kubernetes.io/unschedulable
- node.kubernetes.io/windows-build {#nodekubernetesiowindows-build}
- NodeAddress {#NodeAddress}
- NodeAffinity {#NodeAffinity}
- NodeAllocatableResourceClaimStatus {#NodeAllocatableResourceClaimStatus}
- NodeAllocatableResourceMapping {#NodeAllocatableResourceMapping}
- NodeCondition {#NodeCondition}
- NodeConfigSource {#NodeConfigSource}
- NodeConfigStatus {#NodeConfigStatus}
- NodeDaemonEndpoints {#NodeDaemonEndpoints}
- NodeDeclaredFeatureValidator {#nodedeclaredfeaturevalidator}
- NodeFeatures {#NodeFeatures}
- NodeList {#NodeList}
- nodeName
- NodeRestriction {#noderestriction}
- NodeRuntimeHandler {#NodeRuntimeHandler}
- NodeRuntimeHandlerFeatures {#NodeRuntimeHandlerFeatures}
- Nodes
- Nodes overview
- Nodes to report swap capacity as part of node status
- nodeSelector
- NodeSelector {#NodeSelector}
- NodeSelectorRequirement {#NodeSelectorRequirement}
- NodeSelectorTerm {#NodeSelectorTerm}
- NodeSpec {#NodeSpec}
- NodeStatus {#NodeStatus}
- NodeSwapStatus {#NodeSwapStatus}
- NodeSystemInfo {#NodeSystemInfo}
- nominatedNodeName
- Non-cascading delete
- Non-graceful node shutdown handling {#non-graceful-node-shutdown}
- Non-preempting PriorityClass {#non-preempting-priority-class}
- Non-public IP used for containers
- Non-Template Pod acquisitions
- Non-terminating Pods scope {#quota-scope-non-terminating}
- NonResourceAttributes {#NonResourceAttributes}
- NonResourcePolicyRule {#NonResourcePolicyRule}
- NonResourceRule {#NonResourceRule}
- NormalizeScore {#normalize-scoring}
- Not all objects are in a namespace
- Not possible to join a v1.18 Node to a v1.17 cluster due to missing RBAC
- Not possible to pass a comma separated list of values to arguments inside a `--component-extra-args` flag
- Not-best-effort Pods scope {#quota-scope-non-best-effort}
- Notes
- Notes about PodPriority and existing clusters
- Notes on the strategic merge patch
- Notes on the strategic merge patch using the retainKeys strategy
- Numbered lists
- Numeric comparison operators {#numeric-comparison-operators}
- Object creation denial-of-service {#object-creation-dos}
- Object names
- Object spec and status
- ObjectFieldSelector {#ObjectFieldSelector}
- Objectives
- ObjectMeta {#ObjectMeta}
- ObjectMetricSource {#ObjectMetricSource}
- ObjectMetricStatus {#ObjectMetricStatus}
- ObjectReference {#ObjectReference}
- Observability
- Observability {#observability}
- Observability and metrics
- Observability and runtime security
- Observability for swap use
- Observability of dynamic resources {#observability-dynamic-resources}
- Observe static pod behavior {#behavior-of-static-pods}
- Observe the DRA state
- Off {#updateMode-Off}
- Officially supported client libraries
- Officially-supported Kubernetes client libraries
- On an existing cluster
- OnDelete {#on-delete}
- Opaque Secrets
- OpaqueDeviceConfiguration {#OpaqueDeviceConfiguration}
- Open the Dashboard
- OpenAPI interface definition
- OpenAPI V2
- OpenAPI V3
- OpenID Connect token authentication {#openid-connect-token-authentication}
- Opening a shell when a Pod has more than one container
- OpenShift `kompose convert` example
- openssl
- Operating on a failed deployment
- Operating system support
- Operations
- Operations {#Operations}
- Operations in scope for field management {#apply-and-update}
- Operators
- Operators in Kubernetes
- Opt out of API credential automounting
- Opt-out for higher-level controllers
- Option 1: Scale down the kube-dns-autoscaler deployment to 0 replicas
- Option 2: Delete the kube-dns-autoscaler deployment
- Option 3: Delete the kube-dns-autoscaler manifest file from the master node
- Optional Cluster Services
- Optional ConfigMaps
- Optional kubectl configurations and plugins
- Optional references
- Optional: enable additional DRA API groups {#enable-dra}
- Optionally let _kubectl_ choose the local port {#let-kubectl-choose-local-port}
- Options
- Options inherited from parent commands
- Ordered Pod creation
- Ordered Pod termination
- OrderedReady Pod management
- Ordinal Index
- Organizing resource configurations
- Orphaned dependents
- Other authenticating components
- Other component roles
- Other deployments {#upgrade-other}
- Other kernel requirements {#requirements-other}
- Other languages
- Other local options
- Other Pod conditions {#other-pod-conditions}
- Other possible scenarios
- Other ways to change the replica count
- Others {#authorization-miscellaneous}
- Out of tree
- Out-of-tree volume plugins
- Output options
- Overall approach
- Overhead {#Overhead}
- Overview
- Overview of Kubernetes Services
- Overview of Kustomize
- Overwrite the configuration
- Owner references in object specifications
- Owner references, labels, and finalizers {#owners-labels-finalizers}
- OwnerReference {#OwnerReference}
- OwnerReferencesPermissionEnforcement {#ownerreferencespermissionenforcement}
- Owners and dependents {#owners-dependents}
- Ownership
- Ownership and finalizers
- Ownership and lifecycle
- Package the scheduler
- Parallel authorizers
- Parallel execution for Jobs {#parallel-jobs}
- Parallel Pod management
- Parameter resources
- Parameter tuning
- Parameters
- ParamKind {#ParamKind}
- ParamRef {#ParamRef}
- ParentReference {#ParentReference}
- Partitionable devices {#partitionable-devices}
- Partitioned rolling updates {#partitions}
- Passing custom flags to control plane components {#control-plane-flags}
- Patch only required fields {#patch-required-fields}
- Patching resources
- Path Segment Names
- Path types
- Pause container
- Paused
- Pausing a rollout
- Pausing and resuming a rollout
- Pausing and Resuming a rollout of a Deployment {#pausing-and-resuming-a-deployment}
- Peer-aggregated discovery
- Performance and latency {#performance-latency}
- Performing a rollback on a DaemonSet
- Performing a rolling update
- Performing cleanup {#post-csr-cleanup}
- Periodic review
- Permissive RBAC permissions
- Permit
- Persistence
- Persistent storage {#storage}
- Persistent Volume Claim as Snapshot Source Protection
- Persistent volume creation
- Persistent Volumes
- PersistentVolume {#PersistentVolume}
- PersistentVolume deletion protection finalizer
- PersistentVolume using a Raw Block Volume {#persistent-volume-using-a-raw-block-volume}
- persistentVolumeClaim {#persistentvolumeclaim}
- PersistentVolumeClaim naming
- PersistentVolumeClaim requesting a Raw Block Volume {#persistent-volume-claim-requesting-a-raw-block-volume}
- PersistentVolumeClaim retention
- PersistentVolumeClaimCondition {#PersistentVolumeClaimCondition}
- PersistentVolumeClaimList {#PersistentVolumeClaimList}
- PersistentVolumeClaimResize {#persistentvolumeclaimresize}
- PersistentVolumeClaims
- PersistentVolumeClaimSpec {#PersistentVolumeClaimSpec}
- PersistentVolumeClaimStatus {#PersistentVolumeClaimStatus}
- PersistentVolumeClaimTemplate {#PersistentVolumeClaimTemplate}
- PersistentVolumeClaimVolumeSource {#PersistentVolumeClaimVolumeSource}
- PersistentVolumeList {#PersistentVolumeList}
- PersistentVolumes typed `hostPath`
- PersistentVolumeSpec {#PersistentVolumeSpec}
- PersistentVolumeStatus {#PersistentVolumeStatus}
- Persisting Node object reconfiguration
- Persisting the reconfiguration
- Phase
- Phase 1: Candidate placement generation
- Phase 2: Pod-level filtering and feasibility check
- Phase 3: Placement scoring and selection
- PhotonPersistentDiskVolumeSource {#PhotonPersistentDiskVolumeSource}
- Pick a namespace for the placeholder pods
- PID based eviction
- PID limiting
- Placement scheduling algorithm
- Placing a Pod in the Guaranteed QoS class
- Plan for future updates to fields {#plan-future-field-updates}
- Planning a cluster
- Platform compatibility {#multi-platform}
- Plugin API
- Plugin configuration
- Plugins that apply to multiple extension points {#multipoint}
- Pod
- Pod {#Pod}
- Pod affinity and anti-affinity
- Pod and container level security context configuration {#security-context}
- Pod and container logs {#basic-logging-in-kubernetes}
- Pod backoff failure policy
- Pod behavior during kubelet restarts {#kubelet-restarts}
- Pod conditions
- Pod deletion cost
- Pod Disruption
- Pod disruption budgets
- Pod disruption conditions {#pod-disruption-conditions}
- Pod failure policy {#pod-failure-policy}
- Pod generation
- Pod group priority
- Pod Identity
- Pod index label
- Pod interactions with topology manager policies
- Pod lifecycle
- Pod lifetime
- Pod Management Policies
- Pod management policy
- Pod Name Label
- Pod networking
- Pod OS
- Pod OS field
- Pod overhead
- Pod phase
- Pod PID limits
- Pod placement
- Pod priority
- Pod Priority based graceful node shutdown {#pod-priority-graceful-node-shutdown}
- Pod readiness {#pod-readiness-gate}
- Pod readiness and autoscaling metrics
- Pod readiness to start containers {#pod-ready-to-start-containers}
- Pod resize status
- Pod Resize Status and Retry Logic
- Pod resource checkpoints
- Pod resources API
- Pod resources example {#example-2}
- Pod restart reasons
- Pod scheduling constraints {#provisioning-pod-constraints}
- Pod security
- Pod Security Admission labels for namespaces
- Pod Security levels
- Pod security settings {#pod-security}
- Pod selection for kubelet eviction
- Pod Selector
- Pod shutdown and sidecar containers {#termination-with-sidecars}
- Pod specification adding Raw Block Device path in container
- Pod subresources
- Pod sysctls
- Pod Template
- Pod templates
- Pod Termination Flow {#pod-termination-flow}
- Pod topology labels
- Pod topology spread constraints
- Pod update and replacement
- Pod-level `securityContext` recommendations {#security-context-pod}
- Pod-level resource managers {#pod-level-resource-managers}
- Pod-level resource specification
- Pod-level security isolation
- pod-security.kubernetes.io/audit
- pod-security.kubernetes.io/audit-version
- pod-security.kubernetes.io/audit-violations
- pod-security.kubernetes.io/enforce
- pod-security.kubernetes.io/enforce-policy
- pod-security.kubernetes.io/enforce-version
- pod-security.kubernetes.io/exempt
- pod-security.kubernetes.io/warn
- pod-security.kubernetes.io/warn-version
- Pod-template-hash label
- Pod-wide `securityContext` {#pod-level-security-context}
- Pod's DNS Config {#pod-dns-config}
- Pod's DNS Policy
- Pod's hostname and subdomain fields {#pod-hostname-and-subdomain-field}
- Pod's setHostnameAsFQDN field {#pod-sethostnameasfqdn-field}
- PodAffinity {#PodAffinity}
- PodAffinityTerm {#PodAffinityTerm}
- PodAntiAffinity {#PodAntiAffinity}
- podCertificate projected volumes {#podcertificate}
- PodCertificateProjection {#PodCertificateProjection}
- PodCertificateRequest {#PodCertificateRequest}
- PodCertificateRequestList {#PodCertificateRequestList}
- PodCertificateRequests {#pod-certificate-requests}
- PodCertificateRequestSpec {#PodCertificateRequestSpec}
- PodCertificateRequestStatus {#PodCertificateRequestStatus}
- PodCondition {#PodCondition}
- PodDisruptionBudget {#PodDisruptionBudget}
- PodDisruptionBudget example {#pdb-example}
- PodDisruptionBudgetList {#PodDisruptionBudgetList}
- PodDisruptionBudgetSpec {#PodDisruptionBudgetSpec}
- PodDisruptionBudgetStatus {#PodDisruptionBudgetStatus}
- PodDNSConfig {#PodDNSConfig}
- PodDNSConfigOption {#PodDNSConfigOption}
- PodExtendedResourceClaimStatus {#PodExtendedResourceClaimStatus}
- PodFailurePolicy {#PodFailurePolicy}
- PodFailurePolicyOnExitCodesRequirement {#PodFailurePolicyOnExitCodesRequirement}
- PodFailurePolicyOnPodConditionsPattern {#PodFailurePolicyOnPodConditionsPattern}
- PodFailurePolicyRule {#PodFailurePolicyRule}
- PodGroup
- PodGroup {#PodGroup}
- PodGroup conditions
- PodGroup scheduling algorithm
- PodGroup scheduling cycle
- PodGroupList {#PodGroupList}
- PodGroupResourceClaim {#PodGroupResourceClaim}
- PodGroupSchedulingConstraints {#PodGroupSchedulingConstraints}
- PodGroupSchedulingPolicy {#PodGroupSchedulingPolicy}
- PodGroupSpec {#PodGroupSpec}
- PodGroupStatus {#PodGroupStatus}
- PodGroupTemplate {#PodGroupTemplate}
- PodGroupTemplateReference {#PodGroupTemplateReference}
- PodGroupTemplates
- PodIP {#PodIP}
- PodList {#PodList}
- PodNodeSelector {#podnodeselector}
- PodOS {#PodOS}
- PodReadinessGate {#PodReadinessGate}
- PodReadyToStartContainers {#pod-ready-to-start-containers}
- PodResizePending and PodResizeInProgress {#pod-resize-conditions}
- PodResourceClaim {#PodResourceClaim}
- Pods
- Pods and controllers
- Pods and fault recovery {#pod-fault-recovery}
- Pods are not accessible via their Service IP
- Pods are preempted unnecessarily
- Pods are preempted, but the preemptor is not scheduled
- Pods in `RunContainerError`, `CrashLoopBackOff` or `Error` state
- Pods in a StatefulSet
- Pods overview
- Pods with multiple containers {#how-pods-manage-multiple-containers}
- PodSchedulingGate {#PodSchedulingGate}
- PodSchedulingGroup {#PodSchedulingGroup}
- PodSecurity {#podsecurity}
- PodSecurityContext {#PodSecurityContext}
- PodSecurityPolicy annotations
- PodSecurityPolicy Spec
- PodsMetricSource {#PodsMetricSource}
- PodsMetricStatus {#PodsMetricStatus}
- PodSpec {#PodSpec}
- PodStatus {#PodStatus}
- PodTemplate {#PodTemplate}
- PodTemplateList {#PodTemplateList}
- PodTemplateSpec {#PodTemplateSpec}
- PodTolerationRestriction {#podtolerationrestriction}
- PodTopologyLabels {#podtopologylabels}
- Policies
- Policies for assigning CPUs to Pods
- Policies for assigning memory to Pods {#memory-management-policies}
- Policy actions
- Policy elements
- Policy File Format
- Policy Instantiation
- Policy types
- PolicyRule {#PolicyRule}
- PolicyRulesWithSubjects {#PolicyRulesWithSubjects}
- PoolStatus {#PoolStatus}
- Populate a Volume with data stored in a ConfigMap
- Porcelain
- Port definitions {#field-spec-ports}
- PortStatus {#PortStatus}
- Portworx volume (deprecated) {#portworx-volume}
- portworxVolume (deprecated) {#portworxvolume}
- PortworxVolumeSource {#PortworxVolumeSource}
- Post-upgrade tasks
- PostBind {#post-bind}
- PostFilter {#post-filter}
- Practicing with production-like clusters
- Pre-pulled images
- Pre-scheduled Pods
- PreBind {#pre-bind}
- Preconditions {#Preconditions}
- Preemption
- PreEnqueue {#pre-enqueue}
- PreferredSchedulingTerm {#PreferredSchedulingTerm}
- PreFilter {#pre-filter}
- Preflight checks
- Preparation of credentials by signing CSRs generated by kubeadm
- Prepare the system
- Prepare your cluster for driver installation {#prepare-cluster-driver}
- Preparing CA and service account files
- Preparing the hosts
- Preparing the required container images
- Preparing to install a custom resource
- prependArgs
- Prerequisites
- Prerequisites and installation
- PreScore {#pre-score}
- Preserving the client source IP
- Preset labels
- Pressure Stall Information (PSI) {#psi}
- Pressure Stall Information (PSI) {#requirements-psi}
- Prevent loops caused by competing controllers {#prevent-loops-competing-controllers}
- Prevent plain text retrieval {#cleanup-all-secrets-encrypted}
- Prevent your webhook from triggering itself {#prevent-webhook-self-trigger}
- Preventing containers from loading unwanted kernel modules
- Preventing Pod placement without CSI driver
- Preventing Unauthorized ServiceCIDR Creation/Update using Validating Admission Policy
- Previous storage versions
- Printing State about Workloads
- Prioritizing cluster-essential components
- Priority {#priority}
- Priority and fairness settings {#good-practice-apf-settings}
- Priority Levels
- PriorityClass
- PriorityClass {#PriorityClass}
- PriorityClass scope {#resource-quota-per-priorityclass}
- PriorityClasses
- PriorityClassList {#PriorityClassList}
- PriorityLevelConfiguration
- PriorityLevelConfiguration {#PriorityLevelConfiguration}
- PriorityLevelConfigurationCondition {#PriorityLevelConfigurationCondition}
- PriorityLevelConfigurationList {#PriorityLevelConfigurationList}
- PriorityLevelConfigurationReference {#PriorityLevelConfigurationReference}
- PriorityLevelConfigurationSpec {#PriorityLevelConfigurationSpec}
- PriorityLevelConfigurationStatus {#PriorityLevelConfigurationStatus}
- Privilege escalation prevention and bootstrapping
- Privilege escalation via workload creation or edits {#privilege-escalation-via-pod-creation}
- Privileged
- Privileged containers {#privileged-containers}
- Probe {#Probe}
- Probe mechanism details {#probe-mechanism-details}
- Probe results {#probe-results}
- Probe-level `terminationGracePeriodSeconds` {#probe-level-terminationgraceperiodseconds}
- Problem Daemons
- Production cluster setup
- Production considerations
- Production control plane
- Production environment
- Production user management
- Production worker nodes
- Profile Details
- Profiles
- Programmatic access to the API
- Progress Deadline Seconds
- Progressing Deployment
- Project keys to specific paths and file permissions
- Project Secret keys to specific file paths
- projected
- ProjectedVolumeSource {#ProjectedVolumeSource}
- Propagating cluster-level configuration to each kubelet
- Proportional scaling
- Protect Secret data after reading
- Protect slow starting containers with startup probes {#define-startup-probes}
- Protect system-critical daemons for I/O latency
- Protecting an Application with a PodDisruptionBudget
- Protecting API-based admission resources {#protecting-admission-resources}
- Protecting cluster components from compromise
- Protection for encryption keys
- Protection for Secret data on nodes
- Protobuf serialization
- Providing durable storage
- Providing instance-specific configuration details
- Provisioner
- Provisioning
- Provisioning Volume Snapshot
- Provisioning Volumes from Snapshots
- Proxies
- Proxy
- Proxy modes
- PROXY protocol {#protocol-proxy-special}
- Proxy transport and authentication between API servers {#transport-and-authn}
- Public Disclosure Timing
- Publish Validation Schema in OpenAPI
- Push the image
- pv.kubernetes.io/bind-completed {#pv-kubernetesiobind-completed}
- pv.kubernetes.io/bound-by-controller {#pv-kubernetesioboundby-controller}
- pv.kubernetes.io/migrated-to {#pv-kubernetesio-migratedto}
- pv.kubernetes.io/provisioned-by {#pv-kubernetesiodynamically-provisioned}
- Python client
- Qualifying criteria
- Quality of Service classes
- Quality-of-Service (QoS) {#qos}
- Quantities
- Quantity {#Quantity}
- Questions
- QueueingHint
- QueueSort {#queue-sort}
- Queuing
- QueuingConfiguration {#QueuingConfiguration}
- QuobyteVolumeSource {#QuobyteVolumeSource}
- Quota and Cluster Capacity
- Quota for DRA resource claims
- Quota for extended resources
- Quota for infrastructure resources {#compute-resource-quota}
- Quota for storage
- Quota on object count
- Quota scopes
- Quotas
- Rate limits on eviction
- Raw Block Volume Support
- RawExtension
- rbac.authorization.kubernetes.io/autoupdate
- RBDPersistentVolumeSource {#RBDPersistentVolumeSource}
- RBDVolumeSource {#RBDVolumeSource}
- Re-encrypt Kubernetes secrets using storage version migration
- Read metadata in your application {#read-metadata-application}
- Read-only mounts
- Readiness probe
- Readiness probe {#readiness-probe}
- Real World Example: Configuring Redis using a ConfigMap
- Receiving alerts for security updates and reporting vulnerabilities
- Reclaim policy
- Reclaiming
- Reclaiming node level resources {#reclaim-node-resources}
- Recognizing client certificates
- Recommendations and best practices {#recommendations-best-practices}
- Recommendations and restrictions
- Recommended: `kubectl delete -f <filename>`
- Reconfigure other control plane hosts {#api-server-config-update-more-1}
- Reconfigure other control plane hosts {#api-server-config-update-more-2}
- Reconfigure other control plane hosts {#api-server-config-update-more}
- Reconfiguring the cluster
- Recovering from a failure state
- Recreate {#updateMode-Recreate}
- Recursive operations on local files
- Recursive read-only mounts
- Recursive server scenarios
- Reduced container restart delay
- Reference
- References
- References {#reference}
- Referencing a workload controlling object
- Referring to resources
- Referring to subjects
- Register APIService objects
- Regular expressions in JSONPath
- Reinvocation policy
- Related cluster administrator task
- Related components
- Reliability and availability {#reliability}
- Remove Docker Engine
- Remove the node
- Removed APIs by release
- Renew certificates with external CA
- Renew certificates with the Kubernetes certificates API
- Renewal by using certificate signing requests (CSR)
- Replacing a failed etcd member
- Replicas
- ReplicaSet
- ReplicaSet {#ReplicaSet}
- ReplicaSet as a Horizontal Pod Autoscaler Target
- ReplicaSetCondition {#ReplicaSetCondition}
- ReplicaSetList {#ReplicaSetList}
- ReplicaSetSpec {#ReplicaSetSpec}
- ReplicaSetStatus {#ReplicaSetStatus}
- Replicate the encryption key
- Replication Controller
- ReplicationController
- ReplicationController {#ReplicationController}
- ReplicationControllerCondition {#ReplicationControllerCondition}
- ReplicationControllerList {#ReplicationControllerList}
- ReplicationControllers -- the Old Way
- ReplicationControllerSpec {#ReplicationControllerSpec}
- ReplicationControllerStatus {#ReplicationControllerStatus}
- Report a Vulnerability
- Reporting issues and feature requests
- Request
- Request attributes used in authorization
- Request devices in workloads using DRA {#request-devices-workloads}
- Request filtering {#request-filtering}
- Request flow
- Request Payloads
- Request signing process
- Request verbs and authorization {#determine-the-request-verb}
- Requesting a certificate
- Requesting DRA devices for a PodGroup
- Requesting redirects
- Requests and limits
- Required Fields
- Requirements
- Requiring the `baseline` Pod Security Standard with namespace labels
- Rescheduling
- Reserve {#reserve}
- Reserved memory configuration {#reserved-memory-flag}
- Reserving a PersistentVolume
- Reset workflow {#reset-workflow}
- Resizer
- Resizing by launching replacement Pods
- Resizing container resources
- Resizing Pods {#pod-resize}
- Resource alignment prerequisites
- Resource backends {#resource-backend}
- Resource capacity tracking {#node-capacity}
- Resource constraints
- Resource deletion
- Resource limits
- Resource metrics pipeline
- Resource model
- Resource monitoring for local ephemeral storage
- Resource policies
- Resource pool status {#resource-pool-status}
- Resource requests and limits
- Resource requests and limits of Pod and container
- Resource requirements for etcd
- Resource reservation {#resource-reservation}
- Resource sharing and communication
- Resource sharing within containers
- Resource types
- Resource units in Kubernetes
- Resource URIs
- Resource versions
- resource.kubernetes.io/admin-access {resource-kubernetes-io-admin-access}
- resource.kubernetes.io/pod-claim-name
- ResourceAttributes {#ResourceAttributes}
- ResourceClaim {#ResourceClaim}
- ResourceClaim device status {#resourceclaim-device-status}
- ResourceClaimConsumerReference {#ResourceClaimConsumerReference}
- ResourceClaimList {#ResourceClaimList}
- ResourceClaims and ResourceClaimTemplates {#resourceclaims-templates}
- ResourceClaimSpec {#ResourceClaimSpec}
- ResourceClaimStatus {#ResourceClaimStatus}
- ResourceClaimTemplate {#ResourceClaimTemplate}
- ResourceClaimTemplateList {#ResourceClaimTemplateList}
- ResourceClaimTemplateSpec {#ResourceClaimTemplateSpec}
- ResourceFieldSelector {#ResourceFieldSelector}
- ResourceHealth {#ResourceHealth}
- ResourceMetricSource {#ResourceMetricSource}
- ResourceMetricStatus {#ResourceMetricStatus}
- ResourcePolicyRule {#ResourcePolicyRule}
- ResourcePool {#ResourcePool}
- ResourcePoolStatusRequest {#ResourcePoolStatusRequest}
- ResourcePoolStatusRequestList {#ResourcePoolStatusRequestList}
- ResourcePoolStatusRequestSpec {#ResourcePoolStatusRequestSpec}
- ResourcePoolStatusRequestStatus {#ResourcePoolStatusRequestStatus}
- ResourceQuota {#ResourceQuota}
- ResourceQuota to limit PVC count and cumulative storage capacity
- ResourceQuotaList {#ResourceQuotaList}
- ResourceQuotaSpec {#ResourceQuotaSpec}
- ResourceQuotaStatus {#ResourceQuotaStatus}
- ResourceRequirements {#ResourceRequirements}
- ResourceRule {#ResourceRule}
- Resources
- ResourceSlice {#resourceslice}
- ResourceSliceList {#ResourceSliceList}
- ResourceSliceSpec {#ResourceSliceSpec}
- ResourceStatus {#ResourceStatus}
- Response
- Response compression
- Response headers
- Response latency
- Responsibilities of the ReplicationController
- REST resources (aka API objects)
- Restart
- Restart the kubelet
- Restoring an etcd cluster
- Restrict access to alpha or beta features
- Restrict access to etcd
- Restrict Secret access to specific containers
- Restricted
- Restricted Pod Security Standard changes
- Restricting access to Secrets (deprecated) {#enforce-mountable-secrets}
- Restricting cloud metadata API access
- Restricting network access
- Restrictions
- Restrictions on role binding creation or update
- Restrictions on role creation or update
- Resuming a rollout
- Retrieve the QoS class for a Pod
- Retrieving large results sets in chunks
- Review third party integrations before enabling them
- Revision history
- Revision History Limit
- RFC 1035 Label Names
- RFC 1123 Label Names {#dns-label-names}
- Risks and caveats
- Role {#Role}
- Role and ClusterRole
- Role Based Access Control (RBAC) {#rbac}
- Role of kubectl
- RoleBinding {#RoleBinding}
- RoleBinding and ClusterRoleBinding
- RoleBindingList {#RoleBindingList}
- RoleList {#RoleList}
- RoleRef {#RoleRef}
- Roles for built-in controllers {#controller-roles}
- Roll back an update
- Rolling Back a Deployment
- Rolling Back to a Previous Revision
- Rolling back to a previous revision {#rollback}
- Rolling back to a specific revision
- Rolling back to the previous revision
- Rolling Updates
- Rolling updates overview
- RollingUpdate {#rolling-update}
- RollingUpdateStatefulSetStrategy {#RollingUpdateStatefulSetStrategy}
- Rollover (aka multiple updates in-flight)
- Rotate a decryption key {#rotating-a-decryption-key}
- Rotate infrastructure credentials frequently
- Rotate the CA certificates manually
- Rounding logic when specifying percentages
- Route controller
- Route controller {#authorization-route-controller}
- Rules
- RuleWithOperations {#RuleWithOperations}
- Run `kubeadm join`
- Run a command in a shell
- Run a Pod in the kubelet
- Run a Pod that uses a user namespace {#create-pod}
- Run a Pod that uses an image volume {#create-pod}
- Run and expose php-apache server
- Run Pods that request node capacity
- Run the second scheduler in the cluster
- Run workloads without root privileges {#run-without-root}
- Running an example Job
- Running an example ReplicationController
- Running cloud-controller-manager
- Running commands in a Pod
- Running individual commands in a container
- Running kubeadm without an Internet connection {#without-internet-connection}
- Running Kubernetes inside Rootless Docker/Podman
- Running Kubernetes inside Unprivileged Containers
- Running Node Conformance Test
- Running Node Conformance Test for Other Architectures
- Running Pods on only some Nodes
- Running Pods on select Nodes
- Running Rootless Kubernetes directly on a host
- Running Selected Test
- Running the Job
- Running the link checker
- Runtime classes
- Runtime cost budget
- Runtime protection: access {#protection-runtime-access}
- Runtime protection: compute {#protection-runtime-compute}
- Runtime protection: storage {#protection-runtime-storage}
- RuntimeClass {#RuntimeClass}
- RuntimeClasses
- RuntimeClassList {#RuntimeClassList}
- Safe and Unsafe Sysctls
- Safeguards
- Sandboxing containers
- Sanity testing the ensemble
- Save the kubeadm ClusterConfiguration in a ConfigMap for later reference
- Scalability
- Scale {#Scale}
- Scale Down
- Scale the Web Frontend
- Scale using `kubectl edit`
- Scale using `kubectl patch`
- ScaleIOPersistentVolumeSource {#ScaleIOPersistentVolumeSource}
- ScaleIOVolumeSource {#ScaleIOVolumeSource}
- ScaleSpec {#ScaleSpec}
- ScaleStatus {#ScaleStatus}
- Scaling
- Scaling a Deployment
- Scaling a ReplicaSet
- Scaling a StatefulSet
- Scaling an application
- Scaling cluster infrastructure
- Scaling down
- Scaling down a Deployment
- Scaling down does not work right
- Scaling on custom metrics
- Scaling on multiple metrics
- Scaling out etcd clusters
- Scaling overview
- Scaling policies
- Scaling resources
- Scaling StatefulSets
- Scaling the application by increasing the replica count
- Scaling the number of replicas
- Scaling to zero
- Scaling up
- Scaling up a Deployment
- Scaling up using `kubectl scale`
- Scaling workloads automatically
- Scaling workloads horizontally
- Scaling workloads manually
- Scaling workloads vertically
- Scaling your application
- Scenario: Limiting Storage Consumption
- Schedulable resources and eviction policies
- Schedule a Pod using preferred node affinity
- Schedule a Pod using required node affinity
- Schedule suspension
- Schedule syntax
- Scheduler and allocation controller permissions
- Scheduler authentication & authorization command line options
- Scheduler configuration migrations
- Scheduler flags
- Scheduler networking command line options
- Scheduler TLS command line options
- scheduler.alpha.kubernetes.io/critical-pod (deprecated)
- scheduler.alpha.kubernetes.io/defaultTolerations {#scheduleralphakubernetesio-defaulttolerations}
- scheduler.alpha.kubernetes.io/node-selector {#schedulerkubernetesnode-selector}
- scheduler.alpha.kubernetes.io/preferAvoidPods (deprecated) {#scheduleralphakubernetesio-preferavoidpods}
- scheduler.alpha.kubernetes.io/tolerationsWhitelist {#schedulerkubernetestolerations-whitelist}
- Scheduling
- Scheduling {#Scheduling}
- Scheduling configurations for custom schedulers
- Scheduling cycle & binding cycle
- Scheduling extensions
- Scheduling framework: TAS plugins configuration
- Scheduling overview {#scheduling}
- Scheduling plugins
- Scheduling policy
- ScopedResourceSelectorRequirement {#ScopedResourceSelectorRequirement}
- ScopeSelector {#ScopeSelector}
- Score {#scoring}
- Seats Occupied by a Request
- seccomp
- Seccomp fields
- seccomp.security.alpha.kubernetes.io/pod (non-functional) {#seccomp-security-alpha-kubernetes-io-pod}
- SeccompProfile {#SeccompProfile}
- secret
- Secret {#Secret}
- SecretEnvSource {#SecretEnvSource}
- SecretKeySelector {#SecretKeySelector}
- SecretList {#SecretList}
- SecretProjection {#SecretProjection}
- SecretReference {#SecretReference}
- Secrets
- SecretVolumeSource {#SecretVolumeSource}
- Securing a cluster
- Securing a Pod
- Securing communication
- Securing etcd clusters
- Securing the kubelet
- Securing the Service
- Securing your installation even more {#securing-more}
- Security
- Security Announcements
- Security context options
- Security features in the Linux kernel {#linux-security-features}
- Security profiles & configuration
- Security Vulnerability Response
- SecurityContext {#SecurityContext}
- SecurityContext interactions
- Seek help
- Selectable fields for custom resources {#crd-selectable-fields}
- SelectableField {#SelectableField}
- Selecting storage for optimal performance
- Selector
- Self healing behavior
- Self healing for static pods
- Self-Healing capabilities {#self-healing-capabilities}
- Self-registration of Nodes
- SelfSubjectAccessReview {#SelfSubjectAccessReview}
- SelfSubjectAccessReviewSpec {#SelfSubjectAccessReviewSpec}
- SelfSubjectReview {#SelfSubjectReview}
- SelfSubjectReviewStatus {#SelfSubjectReviewStatus}
- SelfSubjectRulesReview {#SelfSubjectRulesReview}
- SelfSubjectRulesReviewSpec {#SelfSubjectRulesReviewSpec}
- SELinuxOptions {#SELinuxOptions}
- Semantics for **get** and **list**
- Semantics for **watch**
- Send traffic through the frontend
- Sending client traffic
- Separate permissions to DRA related APIs
- Separating Cluster Owner and Application Owner Roles
- Serial and parallel image pulls
- Serialization
- Server certificates
- Server side field validation
- ServerAddressByClientCIDR {#ServerAddressByClientCIDR}
- ServerStorageVersion {#ServerStorageVersion}
- Service {#Service}
- Service account
- Service account issuer discovery
- Service account token audience restriction {#service-account-token-audience-restriction}
- Service Account Token for Image Pulls
- Service account tokens
- Service controller
- Service controller {#authorization-service-controller}
- Service Discovery
- Service Reference
- Service type {#publishing-services-service-types}
- Service type LoadBalancer
- service.alpha.kubernetes.io/tolerate-unready-endpoints (deprecated)
- service.beta.kubernetes.io/aws-load-balancer-access-log-emit-interval (beta) {#service-beta-kubernetes-io-aws-load-balancer-access-log-emit-interval}
- service.beta.kubernetes.io/aws-load-balancer-access-log-enabled (beta) {#service-beta-kubernetes-io-aws-load-balancer-access-log-enabled}
- service.beta.kubernetes.io/aws-load-balancer-access-log-s3-bucket-name (beta) {#service-beta-kubernetes-io-aws-load-balancer-access-log-s3-bucket-name}
- service.beta.kubernetes.io/aws-load-balancer-access-log-s3-bucket-prefix (beta) {#service-beta-kubernetes-io-aws-load-balancer-access-log-s3-bucket-prefix}
- service.beta.kubernetes.io/aws-load-balancer-additional-resource-tags (beta) {#service-beta-kubernetes-io-aws-load-balancer-additional-resource-tags}
- service.beta.kubernetes.io/aws-load-balancer-alpn-policy (beta) {#service-beta-kubernetes-io-aws-load-balancer-alpn-policy}
- service.beta.kubernetes.io/aws-load-balancer-attributes (beta) {#service-beta-kubernetes-io-aws-load-balancer-attributes}
- service.beta.kubernetes.io/aws-load-balancer-backend-protocol (beta) {#service-beta-kubernetes-io-aws-load-balancer-backend-protocol}
- service.beta.kubernetes.io/aws-load-balancer-connection-draining-enabled (beta) {#service-beta-kubernetes-io-aws-load-balancer-connection-draining-enabled}
- service.beta.kubernetes.io/aws-load-balancer-connection-draining-timeout (beta) {#service-beta-kubernetes-io-aws-load-balancer-connection-draining-timeout}
- service.beta.kubernetes.io/aws-load-balancer-connection-idle-timeout (beta) {#service-beta-kubernetes-io-aws-load-balancer-connection-idle-timeout}
- service.beta.kubernetes.io/aws-load-balancer-cross-zone-load-balancing-enabled (beta) {#service-beta-kubernetes-io-aws-load-balancer-cross-zone-load-balancing-enabled}
- service.beta.kubernetes.io/aws-load-balancer-eip-allocations (beta) {#service-beta-kubernetes-io-aws-load-balancer-eip-allocations}
- service.beta.kubernetes.io/aws-load-balancer-extra-security-groups (beta) {#service-beta-kubernetes-io-aws-load-balancer-extra-security-groups}
- service.beta.kubernetes.io/aws-load-balancer-healthcheck-healthy-threshold (beta) {#service-beta-kubernetes-io-aws-load-balancer-healthcheck-healthy-threshold}
- service.beta.kubernetes.io/aws-load-balancer-healthcheck-interval (beta) {#service-beta-kubernetes-io-aws-load-balancer-healthcheck-interval}
- service.beta.kubernetes.io/aws-load-balancer-healthcheck-path (beta) {#service-beta-kubernetes-io-aws-load-balancer-healthcheck-papth}
- service.beta.kubernetes.io/aws-load-balancer-healthcheck-port (beta) {#service-beta-kubernetes-io-aws-load-balancer-healthcheck-port}
- service.beta.kubernetes.io/aws-load-balancer-healthcheck-protocol (beta) {#service-beta-kubernetes-io-aws-load-balancer-healthcheck-protocol}
- service.beta.kubernetes.io/aws-load-balancer-healthcheck-timeout (beta) {#service-beta-kubernetes-io-aws-load-balancer-healthcheck-timeout}
- service.beta.kubernetes.io/aws-load-balancer-healthcheck-unhealthy-threshold (beta) {#service-beta-kubernetes-io-aws-load-balancer-healthcheck-unhealthy-threshold}
- service.beta.kubernetes.io/aws-load-balancer-internal (beta) {#service-beta-kubernetes-io-aws-load-balancer-internal}
- service.beta.kubernetes.io/aws-load-balancer-ip-address-type (beta) {#service-beta-kubernetes-io-aws-load-balancer-ip-address-type}
- service.beta.kubernetes.io/aws-load-balancer-manage-backend-security-group-rules (beta) {#service-beta-kubernetes-io-aws-load-balancer-manage-backend-security-group-rules}
- service.beta.kubernetes.io/aws-load-balancer-name (beta) {#service-beta-kubernetes-io-aws-load-balancer-name}
- service.beta.kubernetes.io/aws-load-balancer-nlb-target-type (beta) {#service-beta-kubernetes-io-aws-load-balancer-nlb-target-type}
- service.beta.kubernetes.io/aws-load-balancer-private-ipv4-addresses (beta) {#service-beta-kubernetes-io-aws-load-balancer-private-ipv4-addresses}
- service.beta.kubernetes.io/aws-load-balancer-proxy-protocol (beta) {#service-beta-kubernetes-io-aws-load-balancer-proxy-protocol}
- service.beta.kubernetes.io/aws-load-balancer-scheme (beta) {#service-beta-kubernetes-io-aws-load-balancer-scheme}
- service.beta.kubernetes.io/aws-load-balancer-security-groups (deprecated) {#service-beta-kubernetes-io-aws-load-balancer-security-groups}
- service.beta.kubernetes.io/aws-load-balancer-ssl-cert (beta) {#service-beta-kubernetes-io-aws-load-balancer-ssl-cert}
- service.beta.kubernetes.io/aws-load-balancer-ssl-negotiation-policy (beta) {#service-beta-kubernetes-io-aws-load-balancer-ssl-negotiation-policy}
- service.beta.kubernetes.io/aws-load-balancer-ssl-ports (beta) {#service-beta-kubernetes-io-aws-load-balancer-ssl-ports}
- service.beta.kubernetes.io/aws-load-balancer-subnets (beta) {#service-beta-kubernetes-io-aws-load-balancer-subnets}
- service.beta.kubernetes.io/aws-load-balancer-target-group-attributes (beta) {#service-beta-kubernetes-io-aws-load-balancer-target-group-attributes}
- service.beta.kubernetes.io/aws-load-balancer-target-node-labels (beta) {#service-beta-kubernetes-io-aws-target-node-labels}
- service.beta.kubernetes.io/aws-load-balancer-type (beta) {#service-beta-kubernetes-io-aws-load-balancer-type}
- service.beta.kubernetes.io/azure-load-balancer-disable-tcp-reset (deprecated) {#service-beta-kubernetes-azure-load-balancer-disble-tcp-reset}
- service.beta.kubernetes.io/load-balancer-source-ranges (deprecated) {#service-beta-kubernetes-io-load-balancer-source-ranges}
- service.kubernetes.io/headless {#servicekubernetesioheadless}
- service.kubernetes.io/service-proxy-name {#servicekubernetesioservice-proxy-name}
- service.kubernetes.io/topology-aware-hints (deprecated) {#servicekubernetesiotopology-aware-hints}
- service.kubernetes.io/topology-mode
- ServiceAccount {#ServiceAccount}
- ServiceAccount admission controller
- ServiceAccount controller
- ServiceAccount permissions {#service-account-permissions}
- ServiceAccount secret tokens {#serviceaccount-secret-tokens}
- ServiceAccount token Secrets
- ServiceAccount token volume projection
- ServiceAccountList {#ServiceAccountList}
- ServiceAccountSubject {#ServiceAccountSubject}
- serviceAccountToken projected volumes {#serviceaccounttoken}
- ServiceAccountTokenProjection {#ServiceAccountTokenProjection}
- ServiceBackendPort {#ServiceBackendPort}
- ServiceCIDR {#ServiceCIDR}
- ServiceCIDRList {#ServiceCIDRList}
- ServiceCIDRSpec {#ServiceCIDRSpec}
- ServiceCIDRStatus {#ServiceCIDRStatus}
- ServiceList {#ServiceList}
- ServicePort {#ServicePort}
- ServiceReference {#ServiceReference}
- Services
- Services and Labels
- Services in Kubernetes
- Services without selectors
- ServiceSpec {#ServiceSpec}
- ServiceStatus {#ServiceStatus}
- Serving multiple versions of a CRD
- Session affinity
- Session stickiness
- Session stickiness timeout
- SessionAffinityConfig {#SessionAffinityConfig}
- Set a small timeout value {#small-timeout}
- Set capabilities for a Container
- Set limits on workload resources
- Set modes, versions and standards
- Set POSIX permissions for Secret keys
- Set references in API objects
- Set the AppArmor Profile for a Container
- Set the desired replica count
- Set the KUBECONFIG environment variable
- Set the Seccomp Profile for a Container
- Set the security context for a Container
- Set the security context for a Pod
- Set the Username for a Container
- Set the Username for a Pod
- Set up a node to support user namespaces
- Set up a signer
- Set up an extension api-server to work with the aggregation layer
- Set up and Expose the Guestbook Frontend
- Set up CRI-O {#cri-o-setup}
- Set up kubelet configuration
- Set up Redis followers
- Set up the etcd cluster
- Set up the first control plane node
- Setting cross-cutting fields
- Setting memory limits
- Setting policies via PodGroupTemplates
- Setting requests and limits for local ephemeral storage {#requests-limits}
- Setting Sysctls for a Pod
- Setting the namespace for a request
- Setting the namespace preference
- Setting the node name
- Setting the threshold
- Setting up local Kubernetes environments
- Setting up Nodes with profiles
- Setting up the cluster
- Setup
- Shard information in responses
- Sharded list and watch {#sharded-list-and-watch}
- ShardInfo {#ShardInfo}
- Should I add a custom resource to my Kubernetes cluster?
- Should I use a ConfigMap or a custom resource?
- Show hidden metrics
- Show the app in the terminal
- Side effects
- Sidebars
- Sidebars and Admonitions
- Sidecar containers and Linux cgroups {#cgroups}
- Sidecar containers and Pod lifecycle
- Sidecar containers in Kubernetes {#pod-sidecar-containers}
- Sidecar containers overview
- Sign
- Sign the CertificateSigningRequest {#sign-the-certificate-signing-request}
- Signer-linked ClusterTrustBundles {#ctb-signer-linked}
- Signer-unlinked ClusterTrustBundles {#ctb-signer-unlinked}
- Signers
- Signing
- Signing certificate signing requests (CSR) generated by kubeadm {#signing-csr}
- Signing CSRs for all certificates
- Simple fanout
- Simplifying with RuntimeClass
- Simulate Pod and Node failure {#simulate-pod-and-node-downtime}
- Single Job starts controller Pod
- Single resource API
- Single root CA
- Single-node etcd cluster
- Slack
- SleepAction {#SleepAction}
- SLI Metrics
- Snapshot using etcdctl options
- snapshot.storage.kubernetes.io/allow-volume-mode-change
- So many proxies
- Some behavior is independent of QoS class {#class-independent-behavior}
- Some filesystem metrics are missing and the metrics format is different
- Sorting list objects
- Source code {#distributing-source-code}
- Source IP for Services with `Type=ClusterIP`
- Source IP for Services with `Type=LoadBalancer`
- Source IP for Services with `Type=NodePort`
- Sources of troubleshooting information
- Special case: migrating the Node IPAM controller {#node-ipam-controller-migration}
- Special cases
- Specific scenarios
- Specify a CPU request and a CPU limit
- Specify a CPU request that is too big for your Nodes
- Specify a memory request and a memory limit
- Specify a memory request that is too big for your Nodes
- Specify both `data` and `stringData`
- Specify multiple versions
- Specify pod priority using a PriorityClass
- Specify schedulers for pods
- Specify unencoded data when creating a Secret
- Specifying `imagePullSecrets` on a Pod
- Specifying a PodDisruptionBudget
- Specifying a scheduling group
- Specifying a structural schema
- Specifying AppArmor confinement
- Specifying application details
- Specifying your own Pod selector
- Spread constraint definition
- SRV records
- SSH authentication Secrets
- SSH tunnels
- Stability
- Stability of workload scale {#flapping}
- Stabilization window
- Stable Network ID
- Stable Storage
- Stack Exchange, Stack Overflow, or Server Fault {#stack-exchange}
- Stacked control plane and etcd nodes
- Stacked etcd topology
- Start a kubelet process configured via the config file
- Start ordinal
- Start up the Redis Database
- Starting a Job with pod-to-pod communication
- Starting a message queue service
- Starting etcd clusters
- Starting Redis
- Starting replication
- Startup probe
- Startup probe {#startup-probe}
- State
- Stateful Applications
- StatefulSet {#StatefulSet}
- StatefulSet considerations
- statefulset.kubernetes.io/pod-name {#statefulsetkubernetesiopod-name}
- StatefulSetCondition {#StatefulSetCondition}
- StatefulSetList {#StatefulSetList}
- StatefulSetOrdinals {#StatefulSetOrdinals}
- StatefulSetPersistentVolumeClaimRetentionPolicy {#StatefulSetPersistentVolumeClaimRetentionPolicy}
- StatefulSetSpec {#StatefulSetSpec}
- StatefulSetStatus {#StatefulSetStatus}
- StatefulSetUpdateStrategy {#StatefulSetUpdateStrategy}
- Stateless Applications
- Static Pods
- Static Pods {#static-pods}
- Static Pods vs DaemonSets {#static-pods-vs-daemonsets}
- Static policy options {#cpu-policy-static--options}
- Static token file {#static-token-file}
- Static token file integration {#static-token-file}
- Status
- Status {#Status}
- Status for Pod readiness
- Status for Pod readiness {#pod-readiness-status}
- StatusCause {#StatusCause}
- StatusDetails {#StatusDetails}
- statusz
- Step 1: Add labels to your nodes
- Step 1: Creating a new Service
- Step 1: Enable the Kubernetes feature gate
- Step 1: Find the DaemonSet revision you want to roll back to
- Step 2: Configure Prometheus
- Step 2: Create the manifest
- Step 2: Roll back to a specific revision
- Step 2: Using labels
- Step 3: Create the DaemonSet
- Step 3: Deleting a service
- Step 3: Watch the progress of the DaemonSet rollback
- Steps for the first control plane node
- Steps for the rest of the control plane nodes
- Stop generating load {#stop-load}
- Stop Signals {#pod-termination-stop-signals}
- Stop the Docker daemon
- Storage
- Storage access for zones
- Storage example
- Storage in Pods {#pod-storage}
- Storage isolation
- Storage Object in Use Protection
- Storage plugins
- Storage version to resource mapping
- Storage versions for custom resources {#CustomResourceDefinition-storage-version}
- storage.alpha.kubernetes.io/migrated-plugins {#storagealphakubernetesiomigrated-plugins}
- StorageClass {#StorageClass}
- StorageClass objects
- storageclass.kubernetes.io/is-default-class
- StorageClassList {#StorageClassList}
- StorageObjectInUseProtection
- StorageOSPersistentVolumeSource {#StorageOSPersistentVolumeSource}
- StorageOSVolumeSource {#StorageOSVolumeSource}
- StorageVersion {#StorageVersion}
- StorageVersionCondition {#StorageVersionCondition}
- StorageVersionList {#StorageVersionList}
- StorageVersionMigration {#StorageVersionMigration}
- StorageVersionMigrationList {#StorageVersionMigrationList}
- StorageVersionMigrationSpec {#StorageVersionMigrationSpec}
- StorageVersionMigrationStatus {#StorageVersionMigrationStatus}
- StorageVersionSpec {#StorageVersionSpec}
- StorageVersionStatus {#StorageVersionStatus}
- Store container fields
- Store Pod fields
- Strategy
- Streaming lists
- Structure Fields
- Structure of a Pod condition
- Structured Logging
- StubDomains and Upstream server Configuration
- Subdividing your cluster using Kubernetes namespaces
- Subject {#Subject}
- SubjectAccessReview {#SubjectAccessReview}
- SubjectAccessReviewSpec {#SubjectAccessReviewSpec}
- SubjectAccessReviewStatus {#SubjectAccessReviewStatus}
- SubjectRulesReviewStatus {#SubjectRulesReviewStatus}
- Subresources
- Success policy {#success-policy}
- SuccessPolicy {#SuccessPolicy}
- SuccessPolicyRule {#SuccessPolicyRule}
- Suggested Configuration Objects
- Suggested defaults
- Summary
- Summary metrics API source {#summary-api-source}
- Summary of features {#summary}
- Support for HorizontalPodAutoscaler in kubectl
- Support for metrics APIs
- Support for resource metrics
- Support for Volumes
- Support hostPort
- Support traffic shaping
- Supported Features
- Supported fields
- Supported operators
- Supported protocols {#protocol-support}
- Supported resource types
- Supporting multiple clusters, users, and authentication mechanisms
- Surviving maintenance
- Suspending a Job
- Swap and control plane nodes
- Swap behavior details
- Swap behaviors
- Swap configuration
- Swap configuration {#swap-configuration}
- Swap discovery using Node Feature Discovery (NFD) {#node-feature-discovery}
- Swap-aware scheduling
- Switch your cluster's storage API version
- Switching from a local encryption provider to the KMS provider
- Switching to another Kubernetes package repository
- Switching to Evented PLEG
- Synopsis
- Syntax
- Syntax and character set
- sysbox
- Sysctl {#Sysctl}
- System accounts
- System component logs
- System requirements
- System Reserved
- systemd cgroup driver {#systemd-cgroup-driver}
- Systemd unit settings
- Tab lists
- Table fetches
- Tables
- Tag catalog {#catalog}
- Tag Reference
- Taint {#Taint}
- Taint based Evictions
- Taint Nodes by Condition
- TaintNodesByCondition {#taintnodesbycondition}
- Taints and tolerations
- Targeting a Namespace by its name
- Targeting a range of ports
- Targeting multiple namespaces by label
- Task context
- TCP probes {#tcp-probes}
- TCPSocketAction {#TCPSocketAction}
- Telemetry and security agent vendors
- Telemetry and security agents
- Template reference
- Tenants
- Terminal Job conditions
- Terminating Pods
- Terminating Pods scope {#quota-scope-terminating}
- Termination of Job pods
- Termination of Pods {#pod-termination}
- Termination process for Pods and their endpoints
- Terminology
- Test access to the service when access label is not defined
- Test minor version upgrades to ensure consistent behavior {#test-minor-version-upgrades}
- Test the installation
- Test the policy {#test-admission-policy-mutation}
- Test the policy {#test-admission-policy-validation}
- Test the service by accessing it from another Pod
- Test webhooks in staging environments {#test-in-staging-environments}
- Test with deprecated APIs disabled
- Testing for liveness
- Testing for readiness
- Testing the message queue service
- The API {#api}
- The etcd API
- The Eviction API {#eviction-api}
- The Ingress resource
- The join workflow {#join-workflow}
- The kubeadm configuration file format
- The KUBECONFIG environment variable
- The kubelet API {#kubelet-api}
- The kubelet drop-in file for systemd
- The Kubernetes model for connecting containers
- The Kubernetes network model
- The NetworkPolicy resource {#networkpolicy-resource}
- The shardSelector field
- The system:masters group
- The two sorts of pod isolation
- The VolumeAttributesClass API
- The VolumeSnapshotClass Resource
- Think about how your application reacts to disruptions
- Third party code and new points of failure
- Third party ingress controllers
- Third-party alternatives
- Time {#Time}
- Time skew
- Time zones
- Timeouts
- TLS
- TLS {#protocol-tls-special}
- TLS Bootstrap
- TLS certificate errors
- TLS problems
- TLS Secrets
- Token controller
- Token Format
- Token Management with kubeadm
- Token request
- TokenRequest {#TokenRequest}
- TokenRequest API
- TokenRequest API tokens {#tokenrequest-api-tokens}
- TokenReview {#TokenReview}
- TokenReviewSpec {#TokenReviewSpec}
- TokenReviewStatus {#TokenReviewStatus}
- Tolerance {#tolerance}
- Tolerating Node failure
- Toleration {#Toleration}
- Tolerations
- Tools
- Topology Awareness
- Topology constraint
- Topology information {#topology}
- Topology manager
- Topology manager policies
- Topology manager policy options
- Topology manager scopes
- Topology manager scopes and policies
- Topology spread constraint examples
- Topology-aware scheduling with basic scheduling policy
- Topology-aware scheduling with gang scheduling policy
- topology.kubernetes.io/region {#topologykubernetesioregion}
- topology.kubernetes.io/zone {#topologykubernetesiozone}
- TopologyConstraint {#TopologyConstraint}
- TopologySelectorLabelRequirement {#TopologySelectorLabelRequirement}
- TopologySelectorTerm {#TopologySelectorTerm}
- TopologySpreadConstraint {#TopologySpreadConstraint}
- Trace Collection
- Traces
- Tracing tools
- Trade-offs
- Traffic distribution control {#traffic-distribution}
- Traffic policies
- Traffic to terminating endpoints
- Transferring ownership
- Transferring ownership between managers
- Transport security
- Troubleshoot `TopologyAffinityError` {#TopologyAffinityError}
- Troubleshooting
- Troubleshooting {#troubleshooting}
- Troubleshooting HostProcess containers
- Troubleshooting stuck evictions
- Troubleshooting the 'No Auth Provider Found' error message {#no-auth-provider-found}
- Troubleshooting with kubectl
- Troubleshooting: Infeasible resize request
- Trusting TLS in a cluster
- TTL mechanism for finished Jobs
- Tune DNS autoscaling parameters {#tuning-autoscaling-parameters}
- Tuning CoreDNS
- Tuning percentageOfNodesToScore
- Tuning the score function
- Type checking
- Type system integration
- TypeChecking {#TypeChecking}
- TypedLocalObjectReference {#TypedLocalObjectReference}
- TypedObjectReference {#TypedObjectReference}
- Types of DRA users {#dra-user-types}
- Types of ephemeral volumes
- Types of Ingress
- Types of Persistent Volumes
- Types of probe {#types-of-probe}
- Types of resource quota
- Types of Secret {#secret-types}
- Types of volumes {#volume-types}
- UIDs
- Unaggregated discovery
- Unavailable resource versions
- Uncordon the node
- UncountedTerminatedPods {#UncountedTerminatedPods}
- Understand feature gate maturity
- Understand the default namespace
- Understanding Cilium components
- Understanding component-specific requirements
- Understanding ConfigMaps and Pods
- Understanding constrained impersonation
- Understanding DaemonSet revisions
- Understanding ephemeral containers
- Understanding etcdctl and etcdutl
- Understanding how DNS horizontal autoscaling works
- Understanding init containers
- Understanding Kubernetes objects {#kubernetes-objects}
- Understanding namespaces and DNS
- Understanding Pod status
- Understanding process namespace sharing
- Understanding PSI Metrics
- Understanding stateful Pod initialization
- Understanding the certificate rotation configuration
- Understanding the encryption at rest configuration
- Understanding the motivation for using namespaces
- Understanding the output
- Understanding user namespaces for pods {#pods-and-userns}
- Unhealthy Pod Eviction Policy
- Uninstall kubectl on macOS
- Uninstall kubectl using homebrew
- Uninstall kubectl using the command-line
- Unsupported forms
- Unsupported TimeZone specification
- Unused PVC tracking
- Unutilized swap space
- Update an object's replica count using `kubectl patch` with `--subresource` {#scale-kubectl-patch}
- Update configuration via a ConfigMap in a multi-container Pod {#rollout-configmap-multiple-containers}
- Update configuration via a ConfigMap in a Pod possessing a sidecar container {#rollout-configmap-sidecar}
- Update configuration via a ConfigMap mounted as a Volume {#rollout-configmap-volume}
- Update configuration via an immutable ConfigMap that is mounted as a volume {#rollout-configmap-immutable-volume}
- Update environment variables of a Pod via a ConfigMap {#rollout-configmap-env}
- Update manifests
- Update modes
- Update strategies
- Update the cgroup driver on all nodes
- Update the preferred storage schema of a CRD
- Update the version of the app
- Updates to existing resources {#patch-and-apply}
- Updating
- Updating a DaemonSet
- Updating a DaemonSet template
- Updating a Deployment
- Updating an application
- Updating an Ingress
- Updating annotations
- Updating images
- Updating labels
- Updating only the container image
- Updating resources
- Updating StatefulSets
- Updating the deployment
- Updating the ensemble
- Updating TTL for finished Jobs
- Updating with `kubectl apply`
- Updating your application without an outage
- Updating your CNI plugins and CNI config files
- Upgrade and downgrade {#upgrade-downgrade}
- Upgrade approaches
- Upgrade Bash
- Upgrade Control Plane
- Upgrade existing objects to a new stored version
- Upgrade fails due to etcd hash not changing
- Upgrade kubeadm
- Upgrade kubelet and kube-proxy
- Upgrade kubelet and kubectl
- Upgrade the kubelet configuration
- Upgrade worker nodes
- Upgrading
- Upgrading an existing cluster with kubeadm
- Upgrading control plane nodes
- Upgrading CoreDNS
- Upgrading etcd clusters
- Upgrading from ABAC
- Upgrading from client-side apply to server-side apply
- Upgrading worker nodes
- Upload the signed certificate
- Uploading a YAML or JSON file
- Uploading control plane certificates to the cluster
- URL
- Usage
- Usage example
- Usage scenarios
- Use `kubectl drain` to remove a node from service
- Use `subPath` (or `subPathExpr`)
- Use a high-availability deployment model {#ha-deployment}
- Use a JSON merge patch to update a Deployment
- Use a load balancer to ensure webhook availability {#load-balancer-webhook}
- Use a named port
- Use a parameter resource
- Use a strategic merge patch to update a Deployment
- Use advanced template parameters
- Use background cascading deletion {#use-background-cascading-deletion}
- Use built-in validation and defaulting for CustomResourceDefinitions {#no-crd-validation-defaulting}
- Use Case
- Use case: dotfiles in a secret volume
- Use case: Secret visible to one container in a Pod
- Use cases
- Use cases for Kubernetes service accounts {#use-cases}
- Use ConfigMap-defined environment variables in Pod commands
- Use container fields as values for environment variables
- Use drivers with seamless upgrade if available
- Use environment variables to define arguments
- Use foreground cascading deletion {#use-foreground-cascading-deletion}
- Use Kompose
- Use kubeadm with CRI runtimes
- Use kubectl to scale StatefulSets
- Use more than one ServiceAccount {#use-multiple-service-accounts}
- Use of a dedicated disk for swap
- Use Pod fields as values for environment variables
- Use raw data
- Use source files
- Use strategic merge patch to update a Deployment using the retainKeys strategy
- Use the default service account to access the API server
- Use the new encryption configuration file
- Use Transport Layer Security (TLS) for all API traffic
- User accounts versus service accounts
- User exposed information
- User Guide
- User impersonation
- User namespaces
- User-facing roles
- UserInfo {#UserInfo}
- Usernetes
- Users in Kubernetes
- UserSubject {#UserSubject}
- Uses for ephemeral containers
- Uses for Secrets
- Using
- Using `--edit` to modify objects before creation
- Using `kubectl describe pod` to fetch details about pods
- Using `kubectl top --show-swap`
- Using `kubectl` in Reusable Scripts
- Using `set` commands to modify objects before creation
- Using a cross-namespace volume data source
- Using a feature
- Using a node logging agent
- Using a plugin
- Using a private registry
- Using a Secret
- Using a service configuration file
- Using a sidecar container with the logging agent {#sidecar-container-with-logging-agent}
- Using a StatefulSet to create a Cassandra ring
- Using an Addon pod to enable Node Problem Detector {#using-addon-pod}
- Using an operator {#using-operators}
- Using cgroup v2 {#using-cgroupv2}
- Using ConfigMaps
- Using Configmaps as environment variables
- Using ConfigMaps as files from a Pod
- Using configurable Container usernames
- Using constrained impersonation
- Using custom certificates {#custom-certificates}
- Using custom images {#custom-images}
- Using Dashboard
- Using device plugins
- Using Dynamic Provisioning
- Using environment variables inside of your config
- Using images from multiple registries
- Using init containers
- Using init phases with kubeadm {#init-phases}
- Using Jobs in real workloads
- Using join phases with kubeadm {#join-phases}
- Using JSONPath expressions with kubectl {#use-with-kubectl}
- Using kubeadm init with a configuration file {#config-file}
- Using kubeadm init with feature gates {#feature-gates}
- Using kubeadm join with a configuration file {#config-file}
- Using kubectl proxy
- Using kubectl to enable Node Problem Detector {#using-kubectl}
- Using kubectl to start a proxy server
- Using labels effectively
- Using multiple Ingress controllers
- Using Official Client Libraries
- Using online playgrounds
- Using Pod failure policy to avoid unnecessary Pod retries {#pod-failure-policy-failjob}
- Using Pod failure policy to avoid unnecessary Pod retries based on custom Pod Conditions {#pod-failure-policy-config-issue}
- Using Pod Failure Policy to avoid unnecessary Pod retries per index {#backoff-limit-per-index-failindex}
- Using Pod failure policy to ignore Pod disruptions {#pod-failure-policy-ignore}
- Using Pods
- Using ReplicationControllers with Services
- Using Secrets as environment variables
- Using Secrets as files from a Pod {#using-secrets-as-files-from-a-pod}
- Using Secrets with static Pods {#restriction-static-pod}
- Using Server-Side Apply in a controller
- Using Service Internal Traffic Policy
- Using sharded list and watch in controllers {#sharded-list-and-watch-controllers}
- Using ssh to create a SOCKS5 proxy
- Using stable network identities
- Using StatefulSets
- Using subPath {#using-subpath}
- Using subPath with expanded environment variables {#using-subpath-expanded-environment}
- Using the `cgroupfs` driver
- Using the built-in Pod Security Admission Controller
- Using the command line runtime package
- Using the List format
- Using this data
- Using volume populators
- v1.16
- v1.22
- v1.25
- v1.26
- v1.27
- v1.29
- v1.32
- Validate addressing
- Validate and monitor
- Validate mutations before admission {#validate-mutations}
- Validate node addressing
- Validate Pod addressing
- Validate Services
- Validating (optional) {#validating}
- Validating the Cassandra StatefulSet
- Validating the Windows cluster operability
- ValidatingAdmissionPolicy {#ValidatingAdmissionPolicy}
- ValidatingAdmissionPolicyBinding {#ValidatingAdmissionPolicyBinding}
- ValidatingAdmissionPolicyBindingList {#ValidatingAdmissionPolicyBindingList}
- ValidatingAdmissionPolicyBindingSpec {#ValidatingAdmissionPolicyBindingSpec}
- ValidatingAdmissionPolicyList {#ValidatingAdmissionPolicyList}
- ValidatingAdmissionPolicySpec {#ValidatingAdmissionPolicySpec}
- ValidatingAdmissionPolicyStatus {#ValidatingAdmissionPolicyStatus}
- ValidatingAdmissionWebhook {#validatingadmissionwebhook}
- ValidatingWebhook {#ValidatingWebhook}
- ValidatingWebhookConfiguration {#ValidatingWebhookConfiguration}
- ValidatingWebhookConfigurationList {#ValidatingWebhookConfigurationList}
- Validation
- Validation {#Validation}
- Validation Expression
- Validation for unrecognized or duplicate fields {#setting-the-field-validation-level}
- Validation ratcheting
- Validation rules
- validation.policy.admission.k8s.io/validation_failure
- ValidationRule {#ValidationRule}
- Variable {#Variable}
- Variable composition
- Verify an update
- Verify contexts
- Verify feature gate configuration
- Verify kubectl configuration
- Verify kubectl helpers
- Verify kubectl setup
- Verify Pod cgroup limits
- Verify that DRA is enabled {#verify}
- Verify that imagePullSecrets are set for new Pods
- Verify that newly written data is encrypted {#verifying-that-data-is-encrypted}
- Verify that the node is healthy
- Verify the DRA driver installation {#verify-driver-install}
- Verify the MAC address and product_uuid are unique for every node {#verify-mac-address}
- Verify the Pod Security Standard enforcement
- Verify the Secret {#verify-the-secret}
- Verify the Software Bill Of Materials
- Verify the status of the cluster
- Verifying and inspecting private claims
- Verifying binary signatures
- Verifying if the Kubernetes package repositories are used
- Verifying image signatures
- Verifying Image Signatures with Admission Controller
- Verifying images for all control plane components
- Verifying that the data is encrypted
- Verifying that the pods were scheduled using the desired schedulers
- Version 2 control groups
- Version compatibility
- Version deprecation
- Version priority
- Version removal
- Version skew policy {#version-skew-policy}
- Vertical workload autoscaling {#vertical-workload-autoscaling}
- View the app
- Viewing and finding resources
- Viewing and Setting Quotas
- Viewing namespaces
- Viewing rollout history
- Viewing the Frontend Service via `kubectl port-forward`
- Viewing the Frontend Service via `LoadBalancer`
- Viewing the kubelet configuration
- Virtual control plane per tenant
- Virtual IP addressing mechanism
- Visualization & Control
- Visualizations with Mermaid
- Volume {#Volume}
- Volume binding mode
- Volume Claim Templates
- Volume Cloning
- Volume expansion {#allow-volume-expansion}
- Volume health monitoring
- Volume Mode
- Volume Modes
- Volume mounts
- Volume Name
- Volume populators and data sources
- Volume snapshot
- Volume Snapshot and Restore Volume from Snapshot Support
- Volume Snapshot Contents
- volume.alpha.kubernetes.io/node-affinity (deprecated) {#volume-alpha-kubernetes-io-node-affinity}
- volume.beta.kubernetes.io/mount-options (deprecated) {#mount-options}
- volume.beta.kubernetes.io/storage-class (deprecated)
- volume.beta.kubernetes.io/storage-provisioner (deprecated)
- volume.kubernetes.io/selected-node
- volume.kubernetes.io/storage-provisioner {#volume-kubernetes-io-storage-provisioner}
- VolumeAttachment {#VolumeAttachment}
- VolumeAttachmentList {#VolumeAttachmentList}
- VolumeAttachmentSource {#VolumeAttachmentSource}
- VolumeAttachmentSpec {#VolumeAttachmentSpec}
- VolumeAttachmentStatus {#VolumeAttachmentStatus}
- VolumeAttributesClass {#VolumeAttributesClass}
- VolumeAttributesClass scope {#quota-scope-volume-attributes-class}
- VolumeAttributesClassList {#VolumeAttributesClassList}
- VolumeDevice {#VolumeDevice}
- VolumeError {#VolumeError}
- VolumeMount {#VolumeMount}
- VolumeNodeAffinity {#VolumeNodeAffinity}
- VolumeNodeResources {#VolumeNodeResources}
- VolumeProjection {#VolumeProjection}
- VolumeResourceRequirements {#VolumeResourceRequirements}
- volumes.kubernetes.io/controller-managed-attach-detach
- VolumeSnapshotClass dependencies
- VolumeSnapshots
- Voluntary and involuntary disruptions
- vSphere
- VsphereVirtualDiskVolumeSource {#VsphereVirtualDiskVolumeSource}
- Wait for the control plane to come up
- Warning about Deployment Configurations
- Watch bookmarks {#watch-bookmarks}
- WatchEvent {#WatchEvent}
- Watching the rolling update status
- Ways of running controllers {#running-controllers}
- Ways to connect
- Web Application With A Database
- Web UI (Dashboard)
- Web-hosted static pod manifest {#pods-created-via-http}
- Webhook backend
- Webhook configuration
- Webhook conversion
- Webhook request and response
- Webhook token authentication
- Webhook token authentication {#webhook-token-authentication}
- WebhookClientConfig {#WebhookClientConfig}
- WebhookConversion {#WebhookConversion}
- WeightedPodAffinityTerm {#WeightedPodAffinityTerm}
- Welcome view
- What about sandboxed Pods?
- What are admission webhooks?
- What are declarative admission policies?
- What are MutatingAdmissionPolicies?
- What are native histograms?
- What are service accounts? {#what-are-service-accounts}
- What are they?
- What can Kubernetes do for you?
- What does each admission controller do?
- What if you specify a container's limit, but not its request?
- What if you specify a container's request, but not its limit?
- What is a Pod?
- What is a PodGroup?
- What is a Workload?
- What is an ephemeral container?
- What is cgroup v2? {#cgroup-v2}
- What is Ingress?
- What is Validating Admission Policy?
- What it does and doesn't check
- What Kubernetes is not
- What Resources Make a Policy
- What to do
- What you can do with kubectl
- What you can't do with network policies (at least, not yet)
- What's next
- What's the difference between a security profile and a security context?
- When draining a node, drain the DRA driver as late as possible
- When it works best
- When Should I NOT Report a Vulnerability?
- When Should I Report a Vulnerability?
- When should I use a Windows HostProcess container?
- When should you use a liveness probe? {#when-should-you-use-a-liveness-probe}
- When should you use a readiness probe? {#when-should-you-use-a-readiness-probe}
- When should you use a startup probe? {#when-should-you-use-a-startup-probe}
- When to use a ReplicaSet
- When to use each probe {#when-to-use-each-probe}
- When to use manual versus automatic scaling
- When to Use Multiple Namespaces
- Where certificates are stored
- Where to look for more details
- Which plugins are enabled by default?
- Why change reclaim policy of a PersistentVolume
- Why change the default storage class?
- Why do I need them?
- Why do some telemetry agents communicate with Docker Engine?
- Why do you need to reserve Service Cluster IPs?
- Why does the kubelet manage the hosts file? {#why-does-kubelet-manage-the-hosts-file}
- Why isn't there a profile between Privileged and Baseline?
- Why should I use `ReadWriteOncePod`?
- Why switch to Evented PLEG?
- Why use manifest-based admission control?
- Why volumes are important
- Why you need Kubernetes and what it can do {#why-you-need-kubernetes-and-what-can-it-do}
- Windows
- Windows distribution channels
- Windows nodes in Kubernetes
- Windows OS version compatibility {#windows-os-version-support}
- Windows PowerShell
- Windows support
- Windows Username limitations
- WindowsSecurityContextOptions {#WindowsSecurityContextOptions}
- With selectors
- Without kubectl proxy
- Without selectors
- Without using a proxy
- Worker node(s) {#node}
- Worker Nodes
- Workflow for Kubernetes {#kubernetes-workflow}
- Workflow for users {#user-workflow}
- Workflow when using `kubeadm init`
- Workflow when using `kubeadm join`
- Working with `impersonate` verb
- Working with Namespaces
- Working with Pods
- Working with ReplicaSets
- Working with ReplicationControllers
- Working with Secrets
- Workload {#Workload}
- Workload autoscalers based on cluster size
- Workload creation
- Workload modifications {#good-practice-workload-modifications}
- Workload placement
- Workload placement considerations
- Workload protection
- Workload resources and Pod templates
- Workload resources for managing pods
- WorkloadList {#WorkloadList}
- WorkloadPodGroupTemplateReference {#WorkloadPodGroupTemplateReference}
- Workloads {#custom-workload}
- WorkloadSpec {#WorkloadSpec}
- Write a conversion webhook server
- Write access for EndpointSlices {#write-access-for-endpoints}
- Write an admission webhook server
- Write an encryption configuration file
- Writing a CronJob spec
- Writing a DaemonSet Spec
- Writing a Deployment Spec
- Writing a Job spec
- Writing a ReplicaSet manifest
- Writing a ReplicationController Manifest
- Writing and reading a termination message
- Writing kubectl plugins
- Writing manifest files {#manifest-files}
- Writing Portable Configuration
- Writing programs for Replication
- Writing the root page for nginx
- Writing to stable storage
- Writing your own operator {#writing-operator}
- Writing, reading, and updating versioned CustomResourceDefinition objects
- X.509 client certificate authentication {#x509-client-certificate-authentication}
- X.509 client certificates {#x509-client-certificates}
- Yahoo Kubectl Flame
- YAML resource encoding {#yaml-encoding}
- z-pages
- ZooKeeper
- ZSH