stackabletech / stackabletech/kafka-operator
Discovery ConfigMap does not expose AuthenticationClass for authenticated access to Kafka brokers
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 28
- Forks
- 8
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 9
Description
Currently, if an AuthenticationClass is set, the client access is encrypted and requires authentication.
This is not exposed in the discovery ConfigMap to be picked up by other operators to configure their Kafka access.
The discovery ConfigMap currently expose one fields:
KAFKA contains the kafka bootstrap servers
Temporary example proposal to add a "secure" field:
KAFKA
AUTHENTICATION_CLASS
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files or tests are named. Start by locating the discovery ConfigMap generation and the existing AuthenticationClass handling, then trace how Kafka connection details are exposed. Done means the ConfigMap exposes the configured authentication information for other operators and the relevant behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kafka, kubernetes, rust
- Domain
- backend, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100