Search Options

Results per page
Sort
Preferred Languages
Labels
Advance

Popular Words: [xss] テスト test %27

Results 431 - 440 of 699 for host:kubernetes.io (0.03 sec)

  1. Kubernetes z-pages | Kubernetes

    Provides runtime diagnostics for Kubernetes components, offering insights into component runtime status and configuration flags.
    kubernetes.io/docs/reference/instrumentation/zpages/
    Registered: Mon Sep 08 23:33:51 UTC 2025
    - 457.4K bytes
    - Viewed (0)
  2. Assign Extended Resources to a Container | Kube...

    FEATURE STATE: Kubernetes v1.34 [stable] This page shows how to assign extended resources to a Container. Before you begin You need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster. It is recommended to run this tutorial on a cluster with at least two nodes that are not acting as control plane hosts. If you do not already have a cluster, you can create one by using minikube or you can use one of these Kubernetes playgrounds:
    kubernetes.io/docs/tasks/configure-pod-container/extended-resource/
    Registered: Mon Sep 08 22:41:21 UTC 2025
    - 471.7K bytes
    - Viewed (0)
  3. Horizontal Pod Autoscaling | Kubernetes

    In Kubernetes, a HorizontalPodAutoscaler automatically updates a workload resource (such as a Deployment or StatefulSet), with the aim of automatically scaling the workload to match demand. Horizontal scaling means that the response to increased load is to deploy more Pods. This is different from vertical scaling, which for Kubernetes would mean assigning more resources (for example: memory or CPU) to the Pods that are already running for the workload.
    kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/
    Registered: Mon Sep 08 22:55:43 UTC 2025
    - 509.7K bytes
    - Viewed (0)
  4. Debugging Kubernetes nodes with crictl | Kubern...

    FEATURE STATE: Kubernetes v1.11 [stable] crictl is a command-line interface for CRI-compatible container runtimes. You can use it to inspect and debug container runtimes and applications on a Kubernetes node. crictl and its source are hosted in the cri-tools repository. Before you begin crictl requires a Linux operating system with a CRI runtime. Installing crictl You can download a compressed archive crictl from the cri-tools release page, for several different architectures.
    kubernetes.io/docs/tasks/debug/debug-cluster/crictl/
    Registered: Mon Sep 08 22:56:15 UTC 2025
    - 468.2K bytes
    - Viewed (0)
  5. Attach Handlers to Container Lifecycle Events |...

    This page shows how to attach handlers to Container lifecycle events. Kubernetes supports the postStart and preStop events. Kubernetes sends the postStart event immediately after a Container is started, and it sends the preStop event immediately before the Container is terminated. A Container may specify one handler per event. Before you begin You need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster.
    kubernetes.io/docs/tasks/configure-pod-container/attach-handler-lifecycle-event/
    Registered: Mon Sep 08 22:56:50 UTC 2025
    - 465.9K bytes
    - Viewed (0)
  6. Connecting Applications with Services | Kubernetes

    The Kubernetes model for connecting containers Now that you have a continuously running, replicated application you can expose it on a network. Kubernetes assumes that pods can communicate with other pods, regardless of which host they land on. Kubernetes gives every pod its own cluster-private IP address, so you do not need to explicitly create links between pods or map container ports to host ports. This means that containers within a Pod can all reach each other's ports on localhost, and all pods in a cluster can see each other without NAT.
    kubernetes.io/docs/tutorials/services/connect-applications-service/
    Registered: Mon Sep 08 23:08:55 UTC 2025
    - 514.3K bytes
    - Viewed (0)
  7. Manage TLS Certificates in a Cluster | Kubernetes

    Kubernetes provides a certificates.k8s.io API, which lets you provision TLS certificates signed by a Certificate Authority (CA) that you control. These CA and certificates can be used by your workloads to establish trust. certificates.k8s.io API uses a protocol that is similar to the ACME draft. Note:Certificates created using the certificates.k8s.io API are signed by a dedicated CA. It is possible to configure your cluster to use the cluster root CA for this purpose, but you should never rely on this.
    kubernetes.io/docs/tasks/tls/managing-tls-in-a-cluster/
    Registered: Mon Sep 08 23:21:49 UTC 2025
    - 482.2K bytes
    - Viewed (0)
  8. Set up Konnectivity service | Kubernetes

    The Konnectivity service provides a TCP level proxy for the control plane to cluster communication. Before you begin You need to have a Kubernetes cluster, and the kubectl command-line tool must be configured to communicate with your cluster. It is recommended to run this tutorial on a cluster with at least two nodes that are not acting as control plane hosts. If you do not already have a cluster, you can create one by using minikube.
    kubernetes.io/docs/tasks/extend-kubernetes/setup-konnectivity/
    Registered: Mon Sep 08 23:23:13 UTC 2025
    - 501.7K bytes
    - Viewed (0)
  9. Node metrics data | Kubernetes

    Mechanisms for accessing metrics at node, volume, pod and container level, as seen by the kubelet.
    kubernetes.io/docs/reference/instrumentation/node-metrics/
    Registered: Mon Sep 08 23:36:16 UTC 2025
    - 459K bytes
    - Viewed (0)
  10. Kubelet Device Manager API Versions | Kubernetes

    This page provides details of version compatibility between the Kubernetes device plugin API, and different versions of Kubernetes itself. Compatibility matrix v1alpha1 v1beta1 Kubernetes 1.21 - ✓ Kubernetes 1.22 - ✓ Kubernetes 1.23 - ✓ Kubernetes 1.24 - ✓ Kubernetes 1.25 - ✓ Kubernetes 1.26 - ✓ Key: ✓ Exactly the same features / API objects in both device plugin API and the Kubernetes version. + The device plugin API has features or API objects that may not be present in the Kubernetes cluster, either because the device plugin API has added additional new API calls, or that the server has removed an old API call.
    kubernetes.io/docs/reference/node/device-plugin-api-versions/
    Registered: Mon Sep 08 23:35:39 UTC 2025
    - 458.2K bytes
    - Viewed (0)
Back to top