This page shows you how to localize the docs for a different language. Contribute to an existing localization You can help add or improve the content of an existing localization. In Kubernetes Slack, you can find a channel for each localization. There is also a general SIG Docs Localizations Slack channel where you can say hello. Note:For extra details on how to contribute to a specific localization, look for a localized version of this page.

Alongside the PR Wrangler, formal approvers, reviewers and members of SIG Docs take week-long shifts triaging and categorising issues for the repository. Duties Each day in a week-long shift the Issue Wrangler will be responsible for: Triaging and tagging incoming issues daily. See Triage and categorize issues for guidelines on how SIG Docs uses metadata. Keeping an eye on stale & rotten issues within the kubernetes/website repository. Maintenance of the Issues board.

SIG Docs approvers take week-long shifts managing pull requests for the repository. This section covers the duties of a PR wrangler. For more information on giving good reviews, see Reviewing changes. Duties Each day in a week-long shift as PR Wrangler: Review open pull requests for quality and adherence to the Style and Content guides. Start with the smallest PRs (size/XS) first, and end with the largest (size/XXL). Review as many PRs as you can.

Resource Types Config Config Config holds the information needed to build connect to remote kubernetes clusters as a given user FieldDescription apiVersionstring/v1 kindstringConfig kind string Legacy field from pkg/api/types.go TypeMeta. TODO(jlowdermilk): remove this after eliminating downstream dependencies. apiVersion string Legacy field from pkg/api/types.go TypeMeta. TODO(jlowdermilk): remove this after eliminating downstream dependencies. preferences [Required] Preferences Preferences holds general information to be use for cli interactions clusters [Required] []NamedCluster Clusters is a map of referencable names to cluster configs

This page explains the two options for configuring the topology of your highly available (HA) Kubernetes clusters. You can set up an HA cluster: With stacked control plane nodes, where etcd nodes are colocated with control plane nodes With external etcd nodes, where etcd runs on separate nodes from the control plane You should carefully consider the advantages and disadvantages of each topology before setting up an HA cluster.

Baseline checklist for ensuring security in Kubernetes clusters.

FEATURE STATE: Kubernetes v1.33 [beta] (enabled by default: true) This page shows how to configure a user namespace for pods. This allows you to isolate 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.

This guide demonstrates how to access the Kubernetes API from within a pod. 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:

Note: This section links to third party projects that provide functionality required by Kubernetes. The Kubernetes project authors aren't responsible for these projects, which are listed alphabetically. To add a project to this list, read the content guide before submitting a change. More information. Kubernetes applications usually consist of multiple, separate services, each running in its own container. Developing and debugging these services on a remote Kubernetes cluster can be cumbersome, requiring you to get a shell on a running container in order to run debugging tools.

This page shows how to investigate problems related to the execution of Init Containers. The example command lines below refer to the Pod as <pod-name> and the Init Containers as <init-container-1> and <init-container-2>. 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.