Synopsis The Kubernetes network proxy runs on each node. This reflects services as defined in the Kubernetes API on each node and can do simple TCP, UDP, and SCTP stream forwarding or round robin TCP, UDP, and SCTP forwarding across a set of backends. Service cluster IPs and ports are currently found through Docker-links-compatible environment variables specifying ports opened by the service proxy. There is an optional addon that provides cluster DNS for these cluster IPs.

Synopsis Display resource (CPU/memory) usage of pods. The 'top pod' command allows you to see the resource consumption of pods. Due to the metrics pipeline delay, they may be unavailable for a few minutes since pod creation. kubectl top pod [NAME | -l label] Examples # Show metrics for all pods in the default namespace kubectl top pod # Show metrics for all pods in the given namespace kubectl top pod --namespace=NAMESPACE # Show metrics for a given pod and its containers kubectl top pod POD_NAME --containers # Show metrics for the pods defined by label name=myLabel kubectl top pod -l name=myLabel Options -A, --all-namespaces If present, list the requested object(s) across all namespaces.

Production-Grade Container Orchestration

Synopsis Update the service account of pod template resources. Possible resources (case insensitive) can be: replicationcontroller (rc), deployment (deploy), daemonset (ds), job, replicaset (rs), statefulset kubectl set serviceaccount (-f FILENAME | TYPE NAME) SERVICE_ACCOUNT Examples # Set deployment nginx-deployment's service account to serviceaccount1 kubectl set serviceaccount deployment nginx-deployment serviceaccount1 # Print the result (in YAML format) of updated nginx deployment with the service account from local file, without hitting the API server kubectl set sa -f nginx-deployment.

Package v1beta2 is the v1beta2 version of the custom_metrics API. Resource Types MetricListOptions MetricValue MetricValueList MetricListOptions MetricListOptions is used to select metrics by their label selectors FieldDescription apiVersionstringcustom.metrics.k8s.io/v1beta2 kindstringMetricListOptions labelSelector string A selector to restrict the list of returned objects by their labels. Defaults to everything. metricLabelSelector string A selector to restrict the list of returned metrics by their labels MetricValue Appears in: MetricValueList MetricValue is the metric value for some object

The Kubernetes Release Comms team (part of SIG Release) looks after release announcements, which go onto the main project blog. After each release, the Release Comms team take over the main blog for a period and publish a series of additional articles to explain or announce changes related to that release. These additional articles are termed post-release comms. Opting in to post-release comms During a release cycle, as a contributor, you can opt in to post-release comms about an upcoming change to Kubernetes.

This page gives writing style guidelines for the Kubernetes documentation. These are guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request. For additional information on creating new content for the Kubernetes documentation, read the Documentation Content Guide. Changes to the style guide are made by SIG Docs as a group. To propose a change or addition, add it to the agenda for an upcoming SIG Docs meeting, and attend the meeting to participate in the discussion.

This page explains the custom Hugo shortcodes that can be used in Kubernetes Markdown documentation. Read more about shortcodes in the Hugo documentation. Feature state In a Markdown page (.md file) on this site, you can add a shortcode to display version and state of the documented feature. Feature state demo Below is a demo of the feature state snippet, which displays the feature as stable in the latest Kubernetes version.

Production-Grade Container Orchestration

Anyone can contribute to Kubernetes. As your contributions to SIG Docs grow, you can apply for different levels of membership in the community. These roles allow you to take on more responsibility within the community. Each role requires more time and commitment. The roles are: Anyone: regular contributors to the Kubernetes documentation Members: can assign and triage issues and provide non-binding review on pull requests Reviewers: can lead reviews on documentation pull requests and can vouch for a change's quality Approvers: can lead reviews on documentation and merge changes Anyone Anyone with a GitHub account can contribute to Kubernetes.