Discovery ConfigMap does not expose AuthenticationClass for authenticated access to Kafka brokers

Open
#467 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
kafka, kubernetes, rust
Domain
backend, infrastructure

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.

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
Dominant language
Rust
Stars
28
Forks
8
Avg merge
2d 12h
Merged PRs (30d)
9

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stackabletech/kafka-operator

All issues in stackabletech/kafka-operator

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.