Search Options

Results per page
Sort
Preferred Languages
Labels
Advance

Popular Words: test ใƒ†ใ‚นใƒˆ

Results 1 - 10 of 660 for host:kubernetes.io (0.02 sec)

  1. 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: 2024-05-17 07:23
    - 425.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: 2024-05-17 07:23
    - 425.5K bytes
    - Viewed (0)
  3. 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: 2024-05-17 07:24
    - 430.7K bytes
    - Viewed (0)
  4. Set up a High Availability etcd Cluster with ku...

    Note:While kubeadm is being used as the management tool for external etcd nodes in this guide, please note that kubeadm does not plan to support certificate rotation or upgrades for such nodes. The long-term plan is to empower the tool etcdadm to manage these aspects. By default, kubeadm runs a local etcd instance on each control plane node. It is also possible to treat the etcd cluster as external and provision etcd instances on separate hosts.
    kubernetes.io/docs/setup/production-environment/tools/kubeadm/setup-ha-etcd-with-kubeadm/
    Registered: 2024-05-17 07:25
    - 443.5K bytes
    - Viewed (0)
  5. 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: 2024-05-17 07:25
    - 420.9K bytes
    - Viewed (0)
  6. 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: 2024-05-17 07:23
    - 420.6K bytes
    - Viewed (0)
  7. 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: 2024-05-17 07:26
    - 432.7K bytes
    - Viewed (0)
  8. 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: 2024-05-17 07:27
    - 420.5K bytes
    - Viewed (0)
  9. Node Status | Kubernetes

    The status of a node in Kubernetes is a critical aspect of managing a Kubernetes cluster. In this article, we'll cover the basics of monitoring and maintaining node status to ensure a healthy and stable cluster. Node status fields A Node's status contains the following information: Addresses Conditions Capacity and Allocatable Info You can use kubectl to view a Node's status and other details: kubectl describe node <insert-node-name-here> Each section of the output is described below.
    kubernetes.io/docs/reference/node/node-status/
    Registered: 2024-05-17 08:08
    - 424.7K bytes
    - Viewed (0)
  10. kubeadm join | Kubernetes

    This command initializes a Kubernetes worker node and joins it to the cluster. Run this on any machine you wish to join an existing cluster Synopsis When joining a kubeadm initialized cluster, we need to establish bidirectional trust. This is split into discovery (having the Node trust the Kubernetes Control Plane) and TLS bootstrap (having the Kubernetes Control Plane trust the Node). There are 2 main schemes for discovery. The first is to use a shared token along with the IP address of the API server.
    kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-join/
    Registered: 2024-05-17 08:07
    - 444.2K bytes
    - Viewed (0)
Back to top