Search Options

Results per page
Sort
Preferred Languages
Labels
Advance

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

Results 1 - 10 of 629 for content_length:[100000 TO 499999] (0.02 sec)

  1. Kubernetes Scheduler | Kubernetes

    In Kubernetes, scheduling refers to making sure that Pods are matched to Nodes so that Kubelet can run them. Scheduling overview A scheduler watches for newly created Pods that have no Node assigned. For every Pod that the scheduler discovers, the scheduler becomes responsible for finding the best Node for that Pod to run on. The scheduler reaches this placement decision taking into account the scheduling principles described below.
    kubernetes.io/docs/concepts/scheduling-eviction/kube-scheduler/
    Registered: 2024-06-14 05:49
    - 422.6K bytes
    - Viewed (0)
  2. Find Out What Container Runtime is Used on a No...

    This page outlines steps to find out what container runtime the nodes in your cluster use. Depending on the way you run your cluster, the container runtime for the nodes may have been pre-configured or you need to configure it. If you're using a managed Kubernetes service, there might be vendor-specific ways to check what container runtime is configured for the nodes. The method described on this page should work whenever the execution of kubectl is allowed.
    kubernetes.io/docs/tasks/administer-cluster/migrating-from-dockershim/find-out-runtime-you-use/
    Registered: 2024-06-14 05:48
    - 421.7K bytes
    - Viewed (0)
  3. Debug Pods | Kubernetes

    This guide is to help users debug applications that are deployed into Kubernetes and not behaving correctly. This is not a guide for people who want to debug their cluster. For that you should check out this guide. Diagnosing the problem The first step in troubleshooting is triage. What is the problem? Is it your Pods, your Replication Controller or your Service? Debugging Pods Debugging Replication Controllers Debugging Services Debugging Pods The first step in debugging a Pod is taking a look at it.
    kubernetes.io/docs/tasks/debug/debug-application/debug-pods/
    Registered: 2024-06-14 05:58
    - 427.8K bytes
    - Viewed (0)
  4. Monitor Node Health | Kubernetes

    Node Problem Detector is a daemon for monitoring and reporting about a node's health. You can run Node Problem Detector as a DaemonSet or as a standalone daemon. Node Problem Detector collects information about node problems from various daemons and reports these conditions to the API server as Node Conditions or as Events. To learn how to install and use Node Problem Detector, see Node Problem Detector project documentation.
    kubernetes.io/docs/tasks/debug/debug-cluster/monitor-node-health/
    Registered: 2024-06-14 05:59
    - 446.6K bytes
    - Viewed (0)
  5. Virtual IPs and Service Proxies | Kubernetes

    Every node in a Kubernetes cluster runs a kube-proxy (unless you have deployed your own alternative component in place of kube-proxy). The kube-proxy component is responsible for implementing a virtual IP mechanism for Services of type other than ExternalName. Each instance of kube-proxy watches the Kubernetes control plane for the addition and removal of Service and EndpointSlice objects. For each Service, kube-proxy calls appropriate APIs (depending on the kube-proxy mode) to configure the node to capture traffic to the Service's clusterIP and port, and redirect that traffic to one of the Service's endpoints (usually a Pod, but possibly an arbitrary user-provided IP address).
    kubernetes.io/docs/reference/networking/virtual-ips/
    Registered: 2024-06-14 06:16
    - 459K bytes
    - Viewed (0)
  6. CRI Pod & Container Metrics | Kubernetes

    Collection of Pod & Container metrics via the CRI.
    kubernetes.io/docs/reference/instrumentation/cri-pod-container-metrics/
    Registered: 2024-06-14 06:16
    - 415.5K bytes
    - Viewed (0)
  7. kubeadm init | Kubernetes

    This command initializes a Kubernetes control-plane node. Run this command in order to set up the Kubernetes control plane Synopsis Run this command in order to set up the Kubernetes control plane The "init" command executes the following phases: preflight Run pre-flight checks certs Certificate generation /ca Generate the self-signed Kubernetes CA to provision identities for other Kubernetes components /apiserver Generate the certificate for serving the Kubernetes API /apiserver-kubelet-client Generate the certificate for the API server to connect to kubelet /front-proxy-ca Generate the self-signed CA to provision identities for front proxy /front-proxy-client Generate the certificate for the front proxy client /etcd-ca Generate the self-signed CA to provision identities for etcd /etcd-server Generate the certificate for serving etcd /etcd-peer Generate the certificate for etcd nodes to communicate with each other /etcd-healthcheck-client Generate the certificate for liveness probes to healthcheck etcd /apiserver-etcd-client Generate the certificate the apiserver uses to access etcd /sa Generate a private key for signing service account tokens along with its public key kubeconfig Generate all kubeconfig files necessary to establish the control plane and the admin kubeconfig file /admin Generate a kubeconfig file for the admin to use and for kubeadm itself /super-admin Generate a kubeconfig file for the super-admin /kubelet Generate a kubeconfig file for the kubelet to use *only* for cluster bootstrapping purposes /controller-manager Generate a kubeconfig file for the controller manager to use /scheduler Generate a kubeconfig file for the scheduler to use etcd Generate static Pod manifest file for local etcd /local Generate the static Pod manifest file for a local, single-node local etcd instance control-plane Generate all static Pod manifest files necessary to establish the control plane /apiserver Generates the kube-apiserver static Pod manifest /controller-manager Generates the kube-controller-manager static Pod manifest /scheduler Generates the kube-scheduler static Pod manifest kubelet-start Write kubelet settings and (re)start the kubelet upload-config Upload the kubeadm and kubelet configuration to a ConfigMap /kubeadm Upload the kubeadm ClusterConfiguration to a ConfigMap /kubelet Upload the kubelet component config to a ConfigMap upload-certs Upload certificates to kubeadm-certs mark-control-plane Mark a node as a control-plane bootstrap-token Generates bootstrap tokens used to join a node to a cluster kubelet-finalize Updates settings relevant to the kubelet after TLS bootstrap /experimental-cert-rotation Enable kubelet client certificate rotation addon Install required addons for passing conformance tests /coredns Install the CoreDNS addon to a Kubernetes cluster /kube-proxy Install the kube-proxy addon to a Kubernetes cluster show-join-command Show the join command for control-plane and worker node kubeadm init [flags] Options --apiserver-advertise-address string The IP address the API Server will advertise it's listening on.
    kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-init/
    Registered: 2024-06-14 06:15
    - 469.6K bytes
    - Viewed (0)
  8. Images | Kubernetes

    A container image represents binary data that encapsulates an application and all its software dependencies. Container images are executable software bundles that can run standalone and that make very well defined assumptions about their runtime environment. You typically create a container image of your application and push it to a registry before referring to it in a Pod. This page provides an outline of the container image concept. Note:If you are looking for the container images for a Kubernetes release (such as v1.
    kubernetes.io/docs/concepts/containers/images/
    Registered: 2024-06-14 05:38
    - 450.6K bytes
    - Viewed (0)
  9. User Namespaces | Kubernetes

    FEATURE STATE: Kubernetes v1.30 [beta] This page explains how user namespaces are used in Kubernetes pods. A user namespace isolates the user running inside the container from the one in the host. A process running as root in a container can run as a different (non-root) user in the host; in other words, the process has full privileges for operations inside the user namespace, but is unprivileged for operations outside the namespace.
    kubernetes.io/docs/concepts/workloads/pods/user-namespaces/
    Registered: 2024-06-14 05:39
    - 430.6K bytes
    - Viewed (0)
  10. DaemonSet | Kubernetes

    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.
    kubernetes.io/docs/concepts/workloads/controllers/daemonset/
    Registered: 2024-06-14 05:40
    - 443.1K bytes
    - Viewed (0)
Back to top