Update docs/modules/opa/pages/usage-guide/operations/pod-disruptions.…

…adoc Co-authored-by: Malte Sander <[email protected]>
stackabletech · Oct 6, 2023 · 7e31047 · 7e31047
1 parent 30d1922
commit 7e31047
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/docs/modules/opa/pages/usage-guide/operations/pod-disruptions.adoc b/docs/modules/opa/pages/usage-guide/operations/pod-disruptions.adoc
@@ -1,5 +1,5 @@
 = Allowed Pod disruptions
 
-For OPA clusters we don't deploy any PodDisruptionBudgets (PDBs), as there is one instance per Kubernetes node running.
+For OPA clusters, the operator does not deploy any PodDisruptionBudgets (PDBs), as there is one instance per Kubernetes node running (Daemonset).
 When a Kubernetes node gets drained to gracefully shut it down, the OPA Pod get's evicted - there is no point in blocking the eviction.
 In case the OPA Pod terminated before the products depending on OPA (e.g. Trino coordinator) on the same node, the products can still use the OPA Service, as it will route to OPA Pods running on other Kubernetes nodes.