Strimzi includes terms which are considered problematic in the modern climate
See original GitHub issueTerms such as whitelist and blacklist should be removed from Strimzis. Kafka has KIP-629 for removing them so some of the work will be dependent on both Kafka and ZooKeeper releases. Where possible we should remove them from APIs, examples and documentation but retain backward compatibility. Some places to apply these changes are:
- The
KafkaMirrorMaker2
CRD containstopicsBlacklistPattern
andgroupsBlacklistPattern
fields - The
KafkaMirrorMaker
CRD containswhitelist
field - The OPA examples in system tests have “whitelist”
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Configuring Strimzi (0.32.0)
Strimzi provides a way to run an Apache Kafka cluster on Kubernetes in various deployment configurations.
Read more >Investigate the usage of divisive language throughout Knative.
Issue open: Strimzi includes terms which are considered problematic in the modern climate strimzi/strimzi-kafka-operator#3289. eventing-ceph
Read more >Accessing Apache Kafka in Strimzi: Part 3 - Red Hat Developer
This third installment of our series on Strimzi looks at Red Hat OpenShift routes and how they can be used with Apache Kafka....
Read more >Strimzi - OperatorHub.io | The registry for Kubernetes Operators
Strimzi provides a way to run an Apache Kafka® cluster on Kubernetes or OpenShift in various deployment configurations.
Read more >Documentation - Apache Kafka
This combination of features means that Kafka consumers are very cheap—they ... of null (which is considered a bad practice) in case the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
For the Kafka related stuff, I would wait for KIP-629 and see how it goes. I think that having consistency is much better so if the KIP will be approved using “include” and “exclude” I would go with that. For OPA stuff, it’s about some examples so we should have more freedom.
Thank you for the response @scholzj !