generated from kubernetes/kubernetes-template-project
-
Notifications
You must be signed in to change notification settings - Fork 180
Closed
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.Indicates an issue or PR lacks a `triage/foo` label and requires one.
Description
What happened:
When leader election is enabled with 3 EPP replicas, updating EPP deployment gets stuck. This is because when leader election is enabled, there is at most 1 ready replica at any given time. Killing the old leader to give the lease to a new leader would violate the default maxUnavailable=25%
in k8s deployment rolling update.
What you expected to happen:
We would need the Recreate
update policy to allow the old leader to be killed and let the new leader take over.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
- Kubernetes version (use
kubectl version
): - Inference extension version (use
git describe --tags --dirty --always
): - Cloud provider or hardware configuration:
- Install tools:
- Others:
Metadata
Metadata
Assignees
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.Indicates an issue or PR lacks a `triage/foo` label and requires one.