From d1952bf98c810acddab068da8c39e36a45d34b94 Mon Sep 17 00:00:00 2001 From: Prasad Katti Date: Thu, 7 May 2020 15:43:37 -0700 Subject: [PATCH] Add feature state for PodDisruptionBudget --- content/en/docs/concepts/workloads/pods/disruptions.md | 2 ++ content/en/docs/tasks/run-application/configure-pdb.md | 2 ++ 2 files changed, 4 insertions(+) diff --git a/content/en/docs/concepts/workloads/pods/disruptions.md b/content/en/docs/concepts/workloads/pods/disruptions.md index 00265e0433..1287763e51 100644 --- a/content/en/docs/concepts/workloads/pods/disruptions.md +++ b/content/en/docs/concepts/workloads/pods/disruptions.md @@ -97,6 +97,8 @@ time as frequent voluntary disruptions. We call this set of features ## How Disruption Budgets Work +{{< feature-state for_k8s_version="v1.5" state="beta" >}} + An Application Owner can create a `PodDisruptionBudget` object (PDB) for each application. A PDB limits the number of pods of a replicated application that are down simultaneously from voluntary disruptions. For example, a quorum-based application would diff --git a/content/en/docs/tasks/run-application/configure-pdb.md b/content/en/docs/tasks/run-application/configure-pdb.md index d33dc24364..d98538c262 100644 --- a/content/en/docs/tasks/run-application/configure-pdb.md +++ b/content/en/docs/tasks/run-application/configure-pdb.md @@ -6,6 +6,8 @@ weight: 110 {{% capture overview %}} +{{< feature-state for_k8s_version="v1.5" state="beta" >}} + This page shows how to limit the number of concurrent disruptions that your application experiences, allowing for higher availability while permitting the cluster administrator to manage the clusters