aws-samples / eks-cluster-upgrade

Automated Amazon EKS cluster upgrade
MIT No Attribution
154 stars 34 forks source link

upgrading EKS cluster hosting Kafka #107

Open hjoshi84 opened 1 year ago

hjoshi84 commented 1 year ago

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

quixoticmonk commented 1 year ago

To clarify, are you asking for a wait state between node upgrades based on user input ?

bryantbiggs commented 1 year ago

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?

hjoshi84 commented 1 year ago

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

hjoshi84 commented 1 year ago

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.

bryantbiggs commented 1 year ago

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?