FEATURE STATE: Kubernetes v1.18 [stable] This page shows how to use the runAsUserName setting for Pods and containers that will run on Windows nodes. This is roughly equivalent of the Linux-specific runAsUser setting, allowing you to run applications in a container as a different username than the default. Before you begin You need to have a Kubernetes cluster and the kubectl command-line tool must be configured to communicate with your cluster.

This page shows how to use a projected Volume to mount several existing volume sources into the same directory. Currently, secret, configMap, downwardAPI, and serviceAccountToken volumes can be projected. Note:serviceAccountToken is not a volume type. 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.

Specify configuration and other data for the Pods that run your workload.

The Kubernetes API server provides API endpoints to indicate the current status of the API server. This page describes these API endpoints and explains how you can use them. API endpoints for health The Kubernetes API server provides 3 API endpoints (healthz, livez and readyz) to indicate the current status of the API server. The healthz endpoint is deprecated (since Kubernetes v1.16), and you should use the more specific livez and readyz endpoints instead.

Services Connecting Applications with Services Using Source IP Explore Termination Behavior for Pods And Their Endpoi...

Applications running in a Kubernetes cluster find and communicate with each other, and the outside world, through the Service abstraction. This document explains what happens to the source IP of packets sent to different types of Services, and how you can toggle this behavior according to your needs. Before you begin Terminology This document makes use of the following terms: NAT Network address translation Source NAT Replacing the source IP on a packet; in this page, that usually means replacing with the IP address of a node.

This page shows how to build the Kubernetes component and tool reference pages. Before you begin Start with the Prerequisites section in the Reference Documentation Quickstart guide. Follow the Reference Documentation Quickstart to generate the Kubernetes component and tool reference pages. What's next Generating Reference Documentation Quickstart Generating Reference Documentation for kubectl Commands Generating Reference Documentation for the Kubernetes API Contributing to the Upstream Kubernetes Project for Documentation

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

Glossary This glossary is intended to be a comprehensive, standardized list of Kubernetes terminology. It includes te...

The Kubernetes documentation follows several types of page content: Concept Task Tutorial Reference Content sections Each page content type contains a number of sections defined by Markdown comments and HTML headings. You can add content headings to your page with the heading shortcode. The comments and headings help maintain the structure of the page content types. Examples of Markdown comments defining page content sections: <!-- overview --> <!-- body --> To create common headings in your content pages, use the heading shortcode with a heading string.