Synopsis The Kubernetes scheduler is a control plane process which assigns Pods to Nodes. The scheduler determines which Nodes are valid placements for each Pod in the scheduling queue according to constraints and available resources. The scheduler then ranks each valid Node and binds the Pod to a suitable Node. Multiple different schedulers may be used within a cluster; kube-scheduler is the reference implementation. See scheduling for more information about scheduling and the kube-scheduler component.

Production-Grade Container Orchestration

Note:Code developers: If you are documenting a new feature for an upcoming Kubernetes release, see Document a new feature. To contribute new content pages or improve existing content pages, open a pull request (PR). Make sure you follow all the requirements in the Before you begin section. If your change is small, or you're unfamiliar with git, read Changes using GitHub to learn how to edit a page. If your changes are large, read Work from a local fork to learn how to make changes locally on your computer.

Resource Types CredentialProviderConfig CredentialProviderConfig CredentialProviderConfig is the configuration containing information about each exec credential provider. Kubelet reads this configuration from disk and enables each provider as specified by the CredentialProvider type. FieldDescription apiVersionstringkubelet.config.k8s.io/v1alpha1 kindstringCredentialProviderConfig providers [Required] []CredentialProvider providers is a list of credential provider plugins that will be enabled by the kubelet. Multiple providers may match against a single image, in which case credentials from all providers will be returned to the kubelet.

SIG Docs Reviewers and Approvers do a few extra things when reviewing a change. Every week a specific docs approver volunteers to triage and review pull requests. This person is the "PR Wrangler" for the week. See the PR Wrangler scheduler for more information. To become a PR Wrangler, attend the weekly SIG Docs meeting and volunteer. Even if you are not on the schedule for the current week, you can still review pull requests (PRs) that are not already under active review.

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.

Anyone can review a documentation pull request. Visit the pull requests section in the Kubernetes website repository to see open pull requests. Reviewing documentation pull requests is a great way to introduce yourself to the Kubernetes community. It helps you learn the code base and build trust with other contributors. Before reviewing, it's a good idea to: Read the content guide and style guide so you can leave informed comments.

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.

Package v1 is the v1 version of the API. Resource Types AdmissionConfiguration AuthorizationConfiguration EncryptionConfiguration AdmissionConfiguration AdmissionConfiguration provides versioned configuration for admission controllers. FieldDescription apiVersionstringapiserver.config.k8s.io/v1 kindstringAdmissionConfiguration plugins []AdmissionPluginConfiguration Plugins allows specifying a configuration per admission control plugin. AuthorizationConfiguration FieldDescription apiVersionstringapiserver.config.k8s.io/v1 kindstringAuthorizationConfiguration authorizers [Required] []AuthorizerConfiguration Authorizers is an ordered list of authorizers to authorize requests against. This is similar to the --authorization-modes kube-apiserver flag Must be at least one. EncryptionConfiguration EncryptionConfiguration stores the complete configuration for encryption providers.

This page describes how kubelet managed Containers can use the Container lifecycle hook framework to run code triggered by events during their management lifecycle. Overview Analogous to many programming language frameworks that have component lifecycle hooks, such as Angular, Kubernetes provides Containers with lifecycle hooks. The hooks enable Containers to be aware of events in their management lifecycle and run code implemented in a handler when the corresponding lifecycle hook is executed.