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.
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
feat: add TopologySpreadConstraints #2202
Conversation
/test limit=local |
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
❗ By default, the pull request is configured to backport to all release branches.
|
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
1 similar comment
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id> |
adding risk label, we should consider where to backport this feat |
/test |
1 similar comment
/test |
@leonardoce, here's the link to the E2E on CNPG workflow run: https://github.com/cloudnative-pg/cloudnative-pg/actions/runs/5179199970 |
/test |
@jsilvela, here's the link to the E2E on CNPG workflow run: https://github.com/cloudnative-pg/cloudnative-pg/actions/runs/5221298277 |
/ok-to-merge |
Closes #2192 Signed-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com>
Signed-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com>
Signed-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com>
Signed-off-by: Jaime Silvela <jaime.silvela@enterprisedb.com>
Since Kubernetes 1.19 the Topology Constraint went to GA, meaning that we can start using it, but this wasn't needed before, now with the latest version 1.26 and 1.27 many things were improved and now we can implement Topology Constraints. Some features may not work since they're available only on 1.26 or above, for any reference please read https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/ to get more information. Closes #2192 Signed-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com> Signed-off-by: Jaime Silvela <jaime.silvela@enterprisedb.com> Co-authored-by: Jaime Silvela <jaime.silvela@enterprisedb.com> (cherry picked from commit 50601b0)
Since Kubernetes 1.19 the Topology Constraint went to GA, meaning that we can start using it, but this wasn't needed before, now with the latest version 1.26 and 1.27 many things were improved and now we can implement Topology Constraints. Some features may not work since they're available only on 1.26 or above, for any reference please read https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/ to get more information. Closes #2192 Signed-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com> Signed-off-by: Jaime Silvela <jaime.silvela@enterprisedb.com> Co-authored-by: Jaime Silvela <jaime.silvela@enterprisedb.com>
Since Kubernetes 1.19 the Topology Constraint went to GA, meaning that we can start using it, but this wasn't needed before, now with the latest version 1.26 and 1.27 many things were improved and now we can implement Topology Constraints. Some features may not work since they're available only on 1.26 or above, for any reference please read https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/ to get more information. Closes #2192 Signed-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com> Signed-off-by: Jaime Silvela <jaime.silvela@enterprisedb.com> Co-authored-by: Jaime Silvela <jaime.silvela@enterprisedb.com>
Closes #2192