-
Notifications
You must be signed in to change notification settings - Fork 1.4k
docs(overview): description list of strimzi advantages #11599
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
base: main
Are you sure you want to change the base?
docs(overview): description list of strimzi advantages #11599
Conversation
Signed-off-by: prmellor <pmellor@redhat.com>
Related to: strimzi/strimzi.github.io#500 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks Paul :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall I think this is great content to add, but there are a few sections that I feel need a few tweaks
Strimzi operators automate rolling upgrades and recovery of Kafka components, helping to reduce manual intervention and downtime. | ||
They also support scaling of Kafka clusters through node pools, automated partition reassignment using Cruise Control to maintain balanced workloads, and safe node removal using the Strimzi Drain Cleaner. | ||
|
||
Full Kafka ecosystem support:: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure about this heading for two reasons:
- Strimzi doesn't provide any specific support for Kafka Streams, so "Full Kafka ecosystem" feels a little confusing
- Under this heading we list Kafka Bridge which is not part of the Kafka ecosystem
Could we use something like "Build data streaming pipelines"
Native Kubernetes integration:: | ||
Strimzi uses operators and Custom Resource Definitions (CRDs) to extend Kubernetes with Kafka-specific capabilities. | ||
This native approach lowers the barrier to adoption and reduces operational overhead, making it easier to deploy and manage Kafka with less manual effort. | ||
|
||
Declarative cluster management:: | ||
Define Kafka clusters, topics, and users as custom resources in YAML. | ||
Custom resources offer a stable and highly configurable way to manage Kafka. | ||
Strimzi operators then automate any updates to these resources. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These two sections feel like they say the same thing to me. Maybe the first one could focus on the use of custom resources in general, and the second could focus on more infrastructure as code for topics and users?
Documentation
Updates overview to explain more about the benefits of using Strimzi, particularly, what an operator-based approach adds over using built-in Kubernetes resources.
Checklist
Please go through this checklist and make sure all applicable tasks have been done