[Verse 1]
When your cluster needs more power, time to scale it right
Add more brokers to the party, keep the data flowing bright
Edit your Kafka resource, bump the replica count
Watch the operator working, new pods it will mount
[Chorus]
Scale up, scale down, brokers join the dance
Reassign partitions, give each topic a chance
Cruise Control balancing, KafkaRebalance way
Connect workers scaling too, it's your Strimzi day
[Verse 2]
But adding brokers isn't magic, partitions stay the same
They won't spread automatically, that's not how we play the game
Manual reassignment needed, or let automation flow
Cruise Control will optimize, the best path it will show
[Chorus]
Scale up, scale down, brokers join the dance
Reassign partitions, give each topic a chance
Cruise Control balancing, KafkaRebalance way
Connect workers scaling too, it's your Strimzi day
[Verse 3]
Create KafkaRebalance custom resource with your goals
Add brokers mode selected, optimization it controls
Pending state it starts with, then proposal phase begins
ProposalReady status shows the rebalancing wins
[Bridge]
Connect clusters scale the same way
Worker pods increase or decrease
Change the replica field today
Watch your throughput find its peace
[Verse 4]
Scaling down needs extra care, remove brokers last to first
Reassign their partitions out, prevent the data burst
Rolling updates keep it smooth, zero downtime is the key
Strimzi handles all the details, scaling made so free
[Chorus]
Scale up, scale down, brokers join the dance
Reassign partitions, give each topic a chance
Cruise Control balancing, KafkaRebalance way
Connect workers scaling too, it's your Strimzi day
[Outro]
From three brokers up to ten
Or scaling back again
Strimzi makes it possible
Kubernetes and Kafka blend