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 option to override default kubernetes scheduler #2013
Conversation
❗ By default, the pull request is configured to backport to all release branches.
|
/test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For some reason it looks like I'm you have a few already merged commits, so this should be rebased before merging, other than that, LGTM
/test |
@phisco, here's the link to the E2E on CNPG workflow run: https://github.com/cloudnative-pg/cloudnative-pg/actions/runs/4967618528 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have to investigate the failures in the e2es
/test |
@phisco, here's the link to the E2E on CNPG workflow run: https://github.com/cloudnative-pg/cloudnative-pg/actions/runs/4973018285 |
Hey, from what I can see, 2 test scenarios didn't execute correctly, it seems to me that this fail is not entirely related to this change, but some timeout/waiting for the cluster to recreate resources. Could you please confirm this and re-run the tests or guide me what might cause such a problem so I can try to fix it? |
/test limit=local |
@armru, here's the link to the E2E on CNPG workflow run: https://github.com/cloudnative-pg/cloudnative-pg/actions/runs/5001495750 |
I would instead prefer to have a rollout when we change the scheduler. The rationale is that if you break the pod configuration, it is better to immediately have a not-working replica and then notice it after months when you need to do a rollout for an unrelated change. |
I agree with @mnencia |
/test limit=local |
@armru, here's the link to the E2E on CNPG workflow run: https://github.com/cloudnative-pg/cloudnative-pg/actions/runs/5004044802 |
Signed-off-by: adrixop95 <adrixop95@me.com>
Signed-off-by: adrixop95 <adrixop95@me.com>
Signed-off-by: adrixop95 <adrixop95@me.com>
Signed-off-by: Philippe Scorsolini <p.scorsolini@gmail.com>
Signed-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com>
Signed-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com>
This patch ensures that we trigger the rollout only needed, the only drawback is that we cannot evaluate the empty string Signed-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com>
/test limit=local |
@armru, here's the link to the E2E on CNPG workflow run: https://github.com/cloudnative-pg/cloudnative-pg/actions/runs/5012278137 |
Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com>
Add the `.spec.schedulerName` field to specify what scheduler should dispatch the Cluster pods. This patch ensures that we trigger a rollout of the pods when the scheduler changes; the only limitation is that no rollout will be started by setting the field empty. Signed-off-by: adrixop95 <adrixop95@me.com> Signed-off-by: Philippe Scorsolini <p.scorsolini@gmail.com> Signed-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com> Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com> Co-authored-by: Philippe Scorsolini <p.scorsolini@gmail.com> Co-authored-by: Armando Ruocco <armando.ruocco@enterprisedb.com> Co-authored-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com> (cherry picked from commit 50113b8)
Add the `.spec.schedulerName` field to specify what scheduler should dispatch the Cluster pods. This patch ensures that we trigger a rollout of the pods when the scheduler changes; the only limitation is that no rollout will be started by setting the field empty. Signed-off-by: adrixop95 <adrixop95@me.com> Signed-off-by: Philippe Scorsolini <p.scorsolini@gmail.com> Signed-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com> Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com> Co-authored-by: Philippe Scorsolini <p.scorsolini@gmail.com> Co-authored-by: Armando Ruocco <armando.ruocco@enterprisedb.com> Co-authored-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com> (cherry picked from commit 50113b8)
Add the `.spec.schedulerName` field to specify what scheduler should dispatch the Cluster pods. This patch ensures that we trigger a rollout of the pods when the scheduler changes; the only limitation is that no rollout will be started by setting the field empty. Signed-off-by: adrixop95 <adrixop95@me.com> Signed-off-by: Philippe Scorsolini <p.scorsolini@gmail.com> Signed-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com> Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com> Co-authored-by: Philippe Scorsolini <p.scorsolini@gmail.com> Co-authored-by: Armando Ruocco <armando.ruocco@enterprisedb.com> Co-authored-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com> (cherry picked from commit 50113b8)
Added the ability to override the default k8s sheduler with a custom one.
Fixes #1863