-
Notifications
You must be signed in to change notification settings - Fork 35
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
upgrading EKS cluster hosting Kafka #107
Comments
To clarify, are you asking for a wait state between node upgrades based on user input ? |
I don't know if this should be handled here - I think this is better handled through the normal Kubernetes highly available constructs such as startup probes, readiness probes, PDBs, etc. How are you deploying Kafka - are you using the Strimzi operator? |
I am using confluent kafka as operator |
Yes. before upgrading the next node script should wait until Kafka pods sync the partitions. otherwise, there will be a loss of data. I believe this will be a good feature addition. |
and how would one check if a kafka pod has finished syncing? isn't this what statefulsets in combination with pod disruption budgets are intended to handle? |
Use case
I am trying to update the EKS cluster hosting Kafka. The script upgraded nodes one by one. Is there any provision where the script can wait some specified time until the next node upgrade or waits till the Kafka partition syncs up?
Solution/User Experience
None
Alternative solutions
No response
The text was updated successfully, but these errors were encountered: