mirror of https://github.com/k3s-io/k3s
![]() 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 |
||
---|---|---|
.. | ||
apps/v1beta1 | ||
authentication.k8s.io/v1beta1 | ||
authorization.k8s.io/v1beta1 | ||
autoscaling/v1 | ||
batch | ||
certificates.k8s.io/v1alpha1 | ||
extensions/v1beta1 | ||
policy/v1beta1 | ||
rbac.authorization.k8s.io/v1alpha1 | ||
storage.k8s.io/v1beta1 | ||
v1 | ||
README.md | ||
labels-annotations-taints.md |
README.md
API Reference
Use the following reference docs to understand the kubernetes REST API for various API group versions:
- v1: operations, model definitions
- extensions/v1beta1: operations, model definitions
- batch/v1: operations, model definitions
- autoscaling/v1: operations, model definitions