Legacy cluster(s) prior to May 31st, 2021” from Confluent Cloud team • Hard deadline for migrating the old cluster to somewhere else • Downtime is inevitable anyway • Pricing plan will be changed
• No access to brokers metrics/configuration - lack of observability • Cluster upgrade just happens - less flexibility on versioning • Some Limitations, or pay for Enterprise Plan
operating applications • Writing a full YAML file for all Kafka components is hard ◦ Kafka/Zookeeper/Connect/MirrorMaker/Bridge/RBAC/... • Application-specific requirements are complex ◦ Cluster configuration ◦ Networking among processes ◦ Distributing mTLS and client certificates
Sandox Project since Aug. 2019 • Core Contributors from Red Hat • Ecosystem & Community are growing • Strimzi Survey 2020: 40% of 40+ users are using it in production
commit the action of updating the current offset position in each partition consumer group a logical group which assures that each partition is only consumed by one member controller one of the brokers that is responsible for electing partition leaders consumer applicatoins or processes which read messages from a broker message the unit of data, which is an array of bytes internally offset a metadata that is an integer value showing which consumers takes messages from partition a single log which appends-only and can be hosted on different servers producer applications or processes which write messages to a broker topic a collection of partitions, “table” in RDBMS and “folder” in FileSystem
supports Authorization using ACLs. You can limit who (users/machines) can do what kind of operations (read/write/admin) on which resources (topics/offset/cluster).
abstraction layter: • Written in Java - no Java professionals within the team (yet) • Software can have a bug • Strimzi should keep supporting the latest version of Kafka ◦ … Strimzi team has been doing great job so far :)