This page provides an storage overview specific to the Windows operating system. Persistent storage Windows has a layered filesystem driver to mount container layers and create a copy filesystem based on NTFS. All file paths in the container are resolved only within the context of that container. With Docker, volume mounts can only target a directory in the container, and not an individual file. This limitation does not apply to containerd.

Concepts for keeping your cloud-native workload secure.

Application logs can help you understand what is happening inside your application. The logs are particularly useful for debugging problems and monitoring cluster activity. Most modern applications have some kind of logging mechanism. Likewise, container engines are designed to support logging. The easiest and most adopted logging method for containerized applications is writing to standard output and standard error streams. However, the native functionality provided by a container engine or runtime is usually not enough for a complete logging solution.

kube-state-metrics, an add-on agent to generate and expose cluster-level metrics.

Production-Grade Container Orchestration

This page explains how to add Linux worker nodes to a kubeadm cluster. Before you begin Each joining worker node has installed the required components from Installing kubeadm, such as, kubeadm, the kubelet and a container runtime. A running kubeadm cluster created by kubeadm init and following the steps in the document Creating a cluster with kubeadm. You need superuser access to the node. Adding Linux worker nodes To add new Linux worker nodes to your cluster do the following for each machine:

This document shares how to validate IPv4/IPv6 dual-stack enabled Kubernetes clusters. Before you begin Provider support for dual-stack networking (Cloud provider or otherwise must be able to provide Kubernetes nodes with routable IPv4/IPv6 network interfaces) A network plugin that supports dual-stack networking. Dual-stack enabled cluster Your Kubernetes server must be at or later than version v1.23. To check the version, enter kubectl version. Note:While you can validate with an earlier version, the feature is only GA and officially supported since v1.

Production-Grade Container Orchestration

Synopsis Create a priority class with the specified name, value, globalDefault and description. kubectl create priorityclass NAME --value=VALUE --global-default=BOOL [--dry-run=server|client|none] Examples # Create a priority class named high-priority kubectl create priorityclass high-priority --value=1000 --description="high priority" # Create a priority class named default-priority that is considered as the global default priority kubectl create priorityclass default-priority --value=1000 --global-default=true --description="default priority" # Create a priority class named high-priority that cannot preempt pods with lower priority kubectl create priorityclass high-priority --value=1000 --description="high priority" --preemption-policy="Never" Options --allow-missing-template-keys     Default: true If true, ignore any errors in templates when a field or map key is missing in the template.

This page provides a list of Kubernetes certified solution providers. From each provider page, you can learn how to install and setup production ready clusters.