Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update High Availability Conventions #779

Closed
wants to merge 1 commit into from
Closed

Update High Availability Conventions #779

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions CONVENTIONS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -139,6 +139,9 @@ Please note that in case of [Single Node OpenShift](https://github.com/openshift
* Hard pod [anti-affinity](https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#always-co-located-in-the-same-node) on hostname (no two pods on the same node)
* Use the maxUnavailable rollout strategy on deployments (prefer 25% by default for a value)
* This is the recommended approach for all the components unless the component needs 3 replicas
* If you let customers change either affinity or replicas, please use this configuration when
* replica count is 2
* customers haven't overridden the affinity
* If the operator or operand requires >= 3 replicas and should be running on worker nodes
* Set soft pod anti-affinity on the hostname so that pods prefer to land on separate nodes (will be violated on two node clusters)
* Use maxSurge for deployments if possible since the spreading rules are soft
Expand Down