-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Only run one replica of controller pods on non-HA clusters #15868
Conversation
Even when running on workers (using IRSA), if we try to run multiple controllers we may have problems with node-spreading, and we don't necessarily gain any availability, as we need an apiserver lease. Issue kubernetes#15852
193d739
to
9daf090
Compare
Assuming we agree with this approach, there is a risk that we break e.g. a PodDisruptionBudget during a rolling update. I propose we merge to 1.28 first, then cherry pick to 1.27 (but not necessarily 1.27.1, as I don't think this is a regression, it only occurs with IRSA + a cluster with a single worker node) |
/test pull-kops-e2e-k8s-gce-ipalias |
/milestone v1.28 |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: johngmyers The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
…-upstream-release-1.28 Automated cherry pick of #15868: Only run one replica of controller pods on non-HA
Even when running on workers (using IRSA), if we try to run multiple
controllers we may have problems with node-spreading, and we don't
necessarily gain any availability, as we need an apiserver lease.
Issue #15852