[Enhancement] Add SASL support to Topic Operator for standalone use
See original GitHub issueI’ve followed the documentation on how to deploy a standalone Topic Operator.
It asks for those variables:
STRIMZI_TRUSTSTORE_LOCATION
STRIMZI_TRUSTSTORE_PASSWORD
STRIMZI_KEYSTORE_LOCATION
STRIMZI_KEYSTORE_PASSWORD
That said, we have a MSK cluster using SCRAM over SASL_SSL (https://docs.aws.amazon.com/msk/latest/developerguide/msk-password.html), we use signed certificates, so we don’t need a store. We also started to work with Confluent Cloud, doing PLAIN over SASL_SSL, also signed certificates.
Is there a way to setup the Topic Operator over those specific scenarios?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:5
- Comments:10 (6 by maintainers)
Top Results From Across the Web
Configuring Strimzi (In Development)
Use ConfigMap resources to add specific configuration to your Strimzi deployment. ... You would use a standalone Topic Operator with a Kafka cluster...
Read more >Chapter 2. Getting started with AMQ Streams
Deploying a standalone Topic Operator and User Operator. Perform these deployment steps if you want to use the Topic Operator and User Operator...
Read more >Configure Metadata Service (MDS) | Confluent Documentation
In the MDS configuration, you should assign the super.users attribute to define a user who has full access to all resources within a...
Read more >Kafka 2.8 Documentation
But we have observed data loss in standalone cluster upgrades when using snapshot.trust.empty=true config. For more details about the issue please refer to ......
Read more >Release Notes for Cisco Identity Services Engine, Release 3.1
Android Settings for Native Supplicant Profile; Enhancements in Audit Logs; Bidirectional Posture Flow; Obtain Configuration Backup Using Cisco Support ...
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
Totally understandable reasoning. Thanks for the clarity, @scholzj !
Would be great to use Strimzi’s Topic and User Operator in our current setup, they are good solutions from a DevOps perspective. Sooner of later I may try to implement this.
Hi @ppatierno,
Does the same apply to the Kafka User operator? We were planning to use both with MSK and SASL_SSL (we have a very similar usecase as OP) but this is a bit of a blocker for us.