Search Options

Results per page
Sort
Preferred Languages
Labels
Advance

Popular Words: test

Results 1 - 10 of 629 for host:kubernetes.io (0.03 sec)

  1. Autoscaling Workloads | Kubernetes

    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.
    kubernetes.io/docs/concepts/workloads/autoscaling/
    Registered: Mon Oct 28 08:40:47 UTC 2024
    - 434.2K bytes
    - Viewed (0)
  2. Finalizers | Kubernetes

    Finalizers are namespaced keys that tell Kubernetes to wait until specific conditions are met before it fully deletes resources marked for deletion. Finalizers alert controllers to clean up resources the deleted object owned. When you tell Kubernetes to delete an object that has finalizers specified for it, the Kubernetes API marks the object for deletion by populating .metadata.deletionTimestamp, and returns a 202 status code (HTTP "Accepted"). The target object remains in a terminating state while the control plane, or other components, take the actions defined by the finalizers.
    kubernetes.io/docs/concepts/overview/working-with-objects/finalizers/
    Registered: Mon Oct 28 08:41:03 UTC 2024
    - 434.6K bytes
    - Viewed (0)
  3. Workloads | Kubernetes

    Understand Pods, the smallest deployable compute object in Kubernetes, and the higher-level abstractions that help you to run them.
    kubernetes.io/docs/concepts/workloads/
    Registered: Mon Oct 28 08:40:33 UTC 2024
    - 430K bytes
    - Viewed (0)
  4. ReplicationController | Kubernetes

    Legacy API for managing workloads that can scale horizontally. Superseded by the Deployment and ReplicaSet APIs.
    kubernetes.io/docs/concepts/workloads/controllers/replicationcontroller/
    Registered: Mon Oct 28 08:41:26 UTC 2024
    - 452.2K bytes
    - Viewed (0)
  5. Container Runtime Interface (CRI) | Kubernetes

    The CRI is a plugin interface which enables the kubelet to use a wide variety of container runtimes, without having a need to recompile the cluster components. You need a working container runtime on each Node in your cluster, so that the kubelet can launch Pods and their containers. The Container Runtime Interface (CRI) is the main protocol for the communication between the kubelet and Container Runtime. The Kubernetes Container Runtime Interface (CRI) defines the main gRPC protocol for the communication between the node components kubelet and container runtime.
    kubernetes.io/docs/concepts/architecture/cri/
    Registered: Mon Oct 28 08:41:23 UTC 2024
    - 429.8K bytes
    - Viewed (0)
  6. Cluster Architecture | Kubernetes

    The architectural concepts behind Kubernetes.
    kubernetes.io/docs/concepts/architecture/
    Registered: Mon Oct 28 08:42:23 UTC 2024
    - 443.8K bytes
    - Viewed (0)
  7. 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 Oct 28 08:42:27 UTC 2024
    - 434.4K bytes
    - Viewed (0)
  8. About cgroup v2 | Kubernetes

    On Linux, control groups constrain resources that are allocated to processes. The kubelet and the underlying container runtime need to interface with cgroups to enforce resource management for pods and containers which includes cpu/memory requests and limits for containerized workloads. There are two versions of cgroups in Linux: cgroup v1 and cgroup v2. cgroup v2 is the new generation of the cgroup API. What is cgroup v2? FEATURE STATE: Kubernetes v1.
    kubernetes.io/docs/concepts/architecture/cgroups/
    Registered: Mon Oct 28 08:42:47 UTC 2024
    - 432.3K bytes
    - Viewed (0)
  9. Container Environment | Kubernetes

    This page describes the resources available to Containers in the Container environment. Container environment The Kubernetes Container environment provides several important resources to Containers: A filesystem, which is a combination of an image and one or more volumes. Information about the Container itself. Information about other objects in the cluster. Container information The hostname of a Container is the name of the Pod in which the Container is running. It is available through the hostname command or the gethostname function call in libc.
    kubernetes.io/docs/concepts/containers/container-environment/
    Registered: Mon Oct 28 08:41:44 UTC 2024
    - 429.5K bytes
    - Viewed (0)
  10. Garbage Collection | Kubernetes

    Garbage collection is a collective term for the various mechanisms Kubernetes uses to clean up cluster resources. This allows the clean up of resources like the following: Terminated pods Completed Jobs Objects without owner references Unused containers and container images Dynamically provisioned PersistentVolumes with a StorageClass reclaim policy of Delete Stale or expired CertificateSigningRequests (CSRs) Nodes deleted in the following scenarios: On a cloud when the cluster uses a cloud controller manager On-premises when the cluster uses an addon similar to a cloud controller manager Node Lease objects Owners and dependents Many objects in Kubernetes link to each other through owner references.
    kubernetes.io/docs/concepts/architecture/garbage-collection/
    Registered: Mon Oct 28 08:44:01 UTC 2024
    - 440.5K bytes
    - Viewed (0)
Back to top