Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
postgres-operator
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Package registry
Model registry
Operate
Terraform modules
Analyze
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
GitHub Mirror
zalando
postgres-operator
Commits
d2a63f33
Commit
d2a63f33
authored
Jun 17, 2019
by
Felix Kunde
Browse files
Options
Downloads
Patches
Plain Diff
address review comments
parent
16b167b7
Branches
coderanger-disruption-budget
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/administrator.md
+5
-3
5 additions, 3 deletions
docs/administrator.md
with
5 additions
and
3 deletions
docs/administrator.md
+
5
−
3
View file @
d2a63f33
...
@@ -158,15 +158,17 @@ data:
...
@@ -158,15 +158,17 @@ data:
By default the operator uses a PodDisruptionBudget (PDB) to protect the cluster
By default the operator uses a PodDisruptionBudget (PDB) to protect the cluster
from voluntarily disruptions and hence unwanted DB downtime. The
`MinAvailable`
from voluntarily disruptions and hence unwanted DB downtime. The
`MinAvailable`
parameter of the PDB is set to
`1`
which
makes it work for
single-node
clusters
parameter of the PDB is set to
`1`
which
prevents killing masters in
single-node
or in situations when there is no master (e.g. standby
cluster
s)
.
clusters and/or the last remaining running instance in a multi-node
cluster.
The PDB is only relaxed in two scenarios:
The PDB is only relaxed in two scenarios:
*
If a cluster is scaled down to
`0`
instances (e.g. for draining nodes)
*
If a cluster is scaled down to
`0`
instances (e.g. for draining nodes)
*
If the PDB is disabled in the configuration (
`enable_pod_disruption_budget`
)
*
If the PDB is disabled in the configuration (
`enable_pod_disruption_budget`
)
The PDB is still in place having
`MinAvailable`
set to
`0`
. If enabled it will
The PDB is still in place having
`MinAvailable`
set to
`0`
. If enabled it will
be automatically set to
`1`
on scale up.
be automatically set to
`1`
on scale up. Disabling PDBs helps avoiding blocking
Kubernetes upgrades in managed K8s environments at the cost of prolonged DB
downtime. See PR #384 for the use case.
### Add cluster-specific labels
### Add cluster-specific labels
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
sign in
to comment