5d4d596667
Automatic merge from submit-queue Use generation in pod disruption budget Fixes #35324 Previously it was possible to use allowedDirsruptions calculated for the previous spec with the current spec. With generation check API servers always make sure that allowedDisruptions were calculated for the current spec. At the same time I set the registry policy to only accept updates if the version based on which the update was made matches to the current version in etcd. That ensures that parallel eviction executions don't use the same allowed disruption. cc: @davidopp @kargakis @wojtek-t |
||
|---|---|---|
| .. | ||
| admin | ||
| api-reference | ||
| design | ||
| devel | ||
| getting-started-guides | ||
| images | ||
| man/man1 | ||
| proposals | ||
| user-guide | ||
| yaml/kubectl | ||
| api.md | ||
| OWNERS | ||
| README.md | ||
| reporting-security-issues.md | ||
| roadmap.md | ||
| troubleshooting.md | ||
| warning.png | ||
| whatisk8s.md | ||
Kubernetes Documentation: releases.k8s.io/HEAD
-
The User's guide is for anyone who wants to run programs and services on an existing Kubernetes cluster.
-
The Cluster Admin's guide is for anyone setting up a Kubernetes cluster or administering it.
-
The Developer guide is for anyone wanting to write programs that access the Kubernetes API, write plugins or extensions, or modify the core code of Kubernetes.
-
The Kubectl Command Line Interface is a detailed reference on the
kubectlCLI. -
The API object documentation is a detailed description of all fields found in core API objects.
-
An overview of the Design of Kubernetes
-
There are example files and walkthroughs in the examples folder.
-
If something went wrong, see the troubleshooting document for how to debug. You should also check the known issues for the release you're using.
-
To report a security issue, see Reporting a Security Issue.