kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #38784 from atiratree/blog-pod-healthy-policy-for-pdbs 

fix nits in blog post: Eviction policy for unhealthy Pods guarded by PDBs
This commit is contained in:
Kubernetes Prow Robot 2023-01-05 09:49:59 -08:00 committed by GitHub
parent 83d7d4e9d3 9e6cb4fe5a
commit 326befd814
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
content/en/blog/_posts/2023-01-06-unhealthy-pod-eviction-policy-for-pdb.md
View File

@ -42,7 +42,7 @@ When enabled, this field lets you support both of those requirements.
API-initiated eviction is the process that triggers graceful pod termination.
The process can be initiated either by calling the API directly,
by using a kubectl drain command, or other actors in the cluster.
by using a `kubectl drain` command, or other actors in the cluster.
During this process every pod removal is consulted with appropriate PDBs,
to ensure that a sufficient number of pods is always running in the cluster.
@ -51,7 +51,8 @@ The following policies allow PDB authors to have a greater control how the proce
There are two policies `IfHealthyBudget` and `AlwaysAllow` to choose from.
The former, `IfHealthyBudget`, follows the existing behavior to achieve the best availability
that you get by default.
that you get by default. Unhealthy pods can be disrupted only if their application
has a minimum available `.status.desiredHealthy` number of pods.
By setting the `spec.unhealthyPodEvictionPolicy` field of your PDB to `AlwaysAllow`,
you are choosing the best effort availability for your application.