- Sort Score
- Result 10 results
- Languages All
- Labels All
Results 91 - 100 of 659 for filetype:html (0.02 sec)
-
Learn Kubernetes Basics | Kubernetes
<!DOCTYPE html> Kubernetes Basics This tutorial provides a walkthrough of the basics of the Kubernetes cluster orchestration system. Each module contains some background information on major Kubernetes features and concepts, and a tutorial for you to follow along. Using the tutorials, you can learn to: Deploy a containerized application on a cluster. Scale the deployment. Update the containerized application with a new software version. Debug the containerized application. What can Kubernetes do for you?kubernetes.io/docs/tutorials/kubernetes-basics/Registered: Fri May 17 07:53:42 UTC 2024 - 420.1K bytes - Viewed (0) -
Use Port Forwarding to Access Applications in a...
This page shows how to use kubectl port-forward to connect to a MongoDB server running in a Kubernetes cluster. This type of connection can be useful for database debugging. 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.kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/Registered: Fri May 17 07:54:51 UTC 2024 - 427.1K bytes - Viewed (0) -
Configure DNS for a Cluster | Kubernetes
Kubernetes offers a DNS cluster addon, which most of the supported environments enable by default. In Kubernetes version 1.11 and later, CoreDNS is recommended and is installed by default with kubeadm. For more information on how to configure CoreDNS for a Kubernetes cluster, see the Customizing DNS Service. An example demonstrating how to use Kubernetes DNS with kube-dns, see the Kubernetes DNS sample plugin.kubernetes.io/docs/tasks/access-application-cluster/configure-dns-cluster/Registered: Fri May 17 07:54:22 UTC 2024 - 416.8K bytes - Viewed (0) -
Networking on Windows | Kubernetes
Kubernetes supports running nodes on either Linux or Windows. You can mix both kinds of node within a single cluster. This page provides an overview to networking specific to the Windows operating system. Container networking on Windows Networking for Windows containers is exposed through CNI plugins. Windows containers function similarly to virtual machines in regards to networking. Each container has a virtual network adapter (vNIC) which is connected to a Hyper-V virtual switch (vSwitch).kubernetes.io/docs/concepts/services-networking/windows-networking/Registered: Fri May 17 07:28:57 UTC 2024 - 430.4K bytes - Viewed (0) -
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: Fri May 17 07:26:28 UTC 2024 - 423.2K 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: Fri May 17 07:27:37 UTC 2024 - 422.7K bytes - Viewed (0) -
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: Fri May 17 07:26:31 UTC 2024 - 420.7K bytes - Viewed (0) -
Cluster Architecture | Kubernetes
The architectural concepts behind Kubernetes.kubernetes.io/docs/concepts/architecture/Registered: Fri May 17 07:28:44 UTC 2024 - 415.9K 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: Fri May 17 07:37:22 UTC 2024 - 435.5K bytes - Viewed (0) -
Upgrading kubeadm clusters | Kubernetes
This page explains how to upgrade a Kubernetes cluster created with kubeadm from version 1.29.x to version 1.30.x, and from version 1.30.x to 1.30.y (where y > x). Skipping MINOR versions when upgrading is unsupported. For more details, please visit Version Skew Policy. To see information about upgrading clusters created using older versions of kubeadm, please refer to following pages instead: Upgrading a kubeadm cluster from 1.28 to 1.29 Upgrading a kubeadm cluster from 1.kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/Registered: Fri May 17 07:37:00 UTC 2024 - 440.8K bytes - Viewed (0)