[Verse 1] When you're planning out your cluster design Controllers are the heart and the spine Three's the magic number for most cases Five for enterprise's larger spaces They coordinate the metadata flow Making sure your brokers always know [Chorus] Three or five controllers, that's the way CPU and memory, don't delay Combined or dedicated, make your choice Network partitions need a careful voice Quorum placement across the racks KRaft topology, cover all the cracks [Verse 2] Hardware specs matter for your controllers CPU cores spinning like propellers Memory gigabytes, four or eight Disk IOPS can't afford to wait Fast SSDs keep the logs in sync Performance matters more than you think [Chorus] Three or five controllers, that's the way CPU and memory, don't delay Combined or dedicated, make your choice Network partitions need a careful voice Quorum placement across the racks KRaft topology, cover all the cracks [Bridge] Combined nodes save you money and space But dedicated gives performance grace When the network splits and chaos starts Quorum keeps the cluster from falling apart Spread across availability zones Never put all controllers in one home [Verse 3] Rack awareness is your safety net Cross-zone placement, don't forget If one goes down, two remain strong Majority rules to keep moving along Plan your topology from the start Network failures won't break the heart [Chorus] Three or five controllers, that's the way CPU and memory, don't delay Combined or dedicated, make your choice Network partitions need a careful voice Quorum placement across the racks KRaft topology, cover all the cracks [Outro] Size it right and plan ahead KRaft controllers keep your cluster fed Topology matters, don't wing it Proper planning helps you win it
← 3 How Strimzi Maps Kafka to Kubernetes Primitives | 2 Configuration Reference →