- Sort Score
- Result 10 results
- Languages All
- Labels All
Results 131 - 140 of 686 for host:kubernetes.io (0.03 sec)
-
Annotations | Kubernetes
You can use Kubernetes annotations to attach arbitrary non-identifying metadata to objects. Clients such as tools and libraries can retrieve this metadata. Attaching metadata to objects You can use either labels or annotations to attach metadata to Kubernetes objects. Labels can be used to select objects and to find collections of objects that satisfy certain conditions. In contrast, annotations are not used to identify and select objects. The metadata in an annotation can be small or large, structured or unstructured, and can include characters not permitted by labels.kubernetes.io/docs/concepts/overview/working-with-objects/annotations/Registered: Mon Jul 07 08:57:18 UTC 2025 - 455.8K bytes - Viewed (0) -
Kubernetes Documentation | Kubernetes
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.io/docs/home/Registered: Mon Jul 07 08:56:11 UTC 2025 - 451.7K bytes - Viewed (0) -
Configuring each kubelet in your cluster using ...
Note: Dockershim has been removed from the Kubernetes project as of release 1.24. Read the Dockershim Removal FAQ for further details. FEATURE STATE: Kubernetes v1.11 [stable] The lifecycle of the kubeadm CLI tool is decoupled from the kubelet, which is a daemon that runs on each node within the Kubernetes cluster. The kubeadm CLI tool is executed by the user when Kubernetes is initialized or upgraded, whereas the kubelet is always running in the background.kubernetes.io/docs/setup/production-environment/tools/kubeadm/kubelet-integration/Registered: Mon Jul 07 08:58:42 UTC 2025 - 463.1K bytes - Viewed (0) -
Validate node setup | Kubernetes
Node Conformance Test Node conformance test is a containerized test framework that provides a system verification and functionality test for a node. The test validates whether the node meets the minimum requirements for Kubernetes; a node that passes the test is qualified to join a Kubernetes cluster. Node Prerequisite To run node conformance test, a node must satisfy the same prerequisites as a standard Kubernetes node. At a minimum, the node should have the following daemons installed:kubernetes.io/docs/setup/best-practices/node-conformance/Registered: Mon Jul 07 08:58:57 UTC 2025 - 453.1K bytes - Viewed (0) -
Certificate Management with kubeadm | Kubernetes
FEATURE STATE: Kubernetes v1.15 [stable] Client certificates generated by kubeadm expire after 1 year. This page explains how to manage certificate renewals with kubeadm. It also covers other tasks related to kubeadm certificate management. The Kubernetes project recommends upgrading to the latest patch releases promptly, and to ensure that you are running a supported minor release of Kubernetes. Following this recommendation helps you to to stay secure. Before you begin You should be familiar with PKI certificates and requirements in Kubernetes.kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-certs/Registered: Mon Jul 07 09:10:34 UTC 2025 - 506.7K bytes - Viewed (0) -
Pod Priority and Preemption | Kubernetes
FEATURE STATE: Kubernetes v1.14 [stable] Pods can have priority. Priority indicates the importance of a Pod relative to other Pods. If a Pod cannot be scheduled, the scheduler tries to preempt (evict) lower priority Pods to make scheduling of the pending Pod possible. Warning:In a cluster where not all users are trusted, a malicious user could create Pods at the highest possible priorities, causing other Pods to be evicted/not get scheduled.kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/Registered: Mon Jul 07 09:14:01 UTC 2025 - 472.4K bytes - Viewed (0) -
Overprovision Node Capacity For A Cluster | Kub...
This page guides you through configuring Node overprovisioning in your Kubernetes cluster. Node overprovisioning is a strategy that proactively reserves a portion of your cluster's compute resources. This reservation helps reduce the time required to schedule new pods during scaling events, enhancing your cluster's responsiveness to sudden spikes in traffic or workload demands. By maintaining some unused capacity, you ensure that resources are immediately available when new pods are created, preventing them from entering a pending state while the cluster scales up.kubernetes.io/docs/tasks/administer-cluster/node-overprovisioning/Registered: Mon Jul 07 09:15:54 UTC 2025 - 467.6K bytes - Viewed (0) -
Changing the Container Runtime on a Node from D...
This task outlines the steps needed to update your container runtime to containerd from Docker. It is applicable for cluster operators running Kubernetes 1.23 or earlier. This also covers an example scenario for migrating from dockershim to containerd. Alternative container runtimes can be picked from this page. Before you begin Note: This section links to third party projects that provide functionality required by Kubernetes. The Kubernetes project authors aren't responsible for these projects, which are listed alphabetically.kubernetes.io/docs/tasks/administer-cluster/migrating-from-dockershim/change-runtime-containerd/Registered: Mon Jul 07 09:16:00 UTC 2025 - 461.6K bytes - Viewed (0) -
Limit Ranges | Kubernetes
By default, containers run with unbounded compute resources on a Kubernetes cluster. Using Kubernetes resource quotas, administrators (also termed cluster operators) can restrict consumption and creation of cluster resources (such as CPU time, memory, and persistent storage) within a specified namespace. Within a namespace, a Pod can consume as much CPU and memory as is allowed by the ResourceQuotas that apply to that namespace. As a cluster operator, or as a namespace-level administrator, you might also be concerned about making sure that a single object cannot monopolize all available resources within a namespace.kubernetes.io/docs/concepts/policy/limit-range/Registered: Mon Jul 07 09:14:43 UTC 2025 - 466.6K bytes - Viewed (0) -
Pod Topology Spread Constraints | Kubernetes
You can use topology spread constraints to control how Pods are spread across your cluster among failure-domains such as regions, zones, nodes, and other user-defined topology domains. This can help to achieve high availability as well as efficient resource utilization. You can set cluster-level constraints as a default, or configure topology spread constraints for individual workloads. Motivation Imagine that you have a cluster of up to twenty nodes, and you want to run a workload that automatically scales how many replicas it uses.kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/Registered: Mon Jul 07 09:16:56 UTC 2025 - 505.7K bytes - Viewed (0)