This page contains guidelines for Kubernetes documentation. If you have questions about what's allowed, join the #sig-docs channel in Kubernetes Slack and ask! You can register for Kubernetes Slack at https://slack.k8s.io/. For information on creating new content for the Kubernetes docs, follow the style guide. Overview Source for the Kubernetes website, including the docs, resides in the kubernetes/website repository. Located in the kubernetes/website/content/<language_code>/docs folder, the majority of Kubernetes documentation is specific to the Kubernetes project.

Resource Types Configuration Configuration Configuration provides configuration for the EventRateLimit admission controller. FieldDescription apiVersionstringeventratelimit.admission.k8s.io/v1alpha1 kindstringConfiguration limits [Required] []Limit limits are the limits to place on event queries received. Limits can be placed on events received server-wide, per namespace, per user, and per source+object. At least one limit is required. Limit Appears in: Configuration Limit is the configuration for a particular limit type FieldDescription type [Required] LimitType type is the type of limit to which this configuration applies

This page contains information about the kubernetes.io analytics dashboard. View the dashboard. This dashboard is built using Google Looker Studio and shows information collected on kubernetes.io using Google Analytics 4 since August 2022. Using the dashboard By default, the dashboard shows all collected analytics for the past 30 days. Use the date selector to see data from a different date range. Other filtering options allow you to view data based on user location, the device used to access the site, the translation of the docs used, and more.

Package v1beta1 is the v1beta1 version of the metrics API. Resource Types NodeMetrics NodeMetricsList PodMetrics PodMetricsList NodeMetrics Appears in: NodeMetricsList NodeMetrics sets resource usage metrics of a node. FieldDescription apiVersionstringmetrics.k8s.io/v1beta1 kindstringNodeMetrics metadata meta/v1.ObjectMeta Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata Refer to the Kubernetes API documentation for the fields of the metadata field. timestamp [Required] meta/v1.Time The following fields define time interval from which metrics were collected from the interval [Timestamp-Window, Timestamp].

Resource Types CloudControllerManagerConfiguration LeaderMigrationConfiguration KubeControllerManagerConfiguration ClientConnectionConfiguration Appears in: KubeSchedulerConfiguration GenericControllerManagerConfiguration ClientConnectionConfiguration contains details for constructing a client. FieldDescription kubeconfig [Required] string kubeconfig is the path to a KubeConfig file. acceptContentTypes [Required] string acceptContentTypes defines the Accept header sent by clients when connecting to a server, overriding the default value of 'application/json'. This field will control all connections to the server used by a particular client. contentType [Required] string contentType is the content type used when sending data to the server from this client.

Production-Grade Container Orchestration

A Secret is an object that contains a small amount of sensitive data such as a password, a token, or a key. Such information might otherwise be put in a Pod specification or in a container image. Using a Secret means that you don't need to include confidential data in your application code. Because Secrets can be created independently of the Pods that use them, there is less risk of the Secret (and its data) being exposed during the workflow of creating, viewing, and editing Pods.

This page provides an overview of init containers: specialized containers that run before app containers in a Pod. Init containers can contain utilities or setup scripts not present in an app image. You can specify init containers in the Pod specification alongside the containers array (which describes app containers). In Kubernetes, a sidecar container is a container that starts before the main application container and continues to run. This document is about init containers: containers that run to completion during Pod initialization.

FEATURE STATE: Kubernetes v1.33 [stable] (enabled by default: true) Sidecar containers are the secondary containers that run along with the main application container within the same Pod. These containers are used to enhance or to extend the functionality of the primary app container by providing additional services, or functionality such as logging, monitoring, security, or data synchronization, without directly altering the primary application code. Typically, you only have one app container in a Pod.

Security architecture information relating to the API server and other components