Skip to content

docs: Highlight security limitations for management access - #1076

Merged
labrenbe merged 2 commits into
mainfrom
docs/add-management-access-warning
Nov 20, 2026
Merged

labrenbe merged 2 commits into
mainfrom
docs/add-management-access-warning

Conversation

@labrenbe

Copy link
Copy Markdown
Member

Description

  • Recommend using secret classes for management access only in dev/test environments
  • Document that management access effectively replaces Kafka's access controls with k8s RBAC

@labrenbe labrenbe self-assigned this Nov 20, 2026
@labrenbe labrenbe moved this to Development: Waiting for Review in Stackable Engineering Nov 20, 2026
@sbernauer

sbernauer commented Nov 20, 2026 •

Copy link
Copy Markdown
Member

To me it's conceptionally totally fine to use a SecretClass to get "your" cert. If we switch this to a Secret I have to start explaining all customers to use a SecretClass instead. This change IMHO worsens the UX. Guess what we are using in the demo ;)

The real problem is that Kafka only looks at the subject and not the SAN entries. I'm not really blocking this change, but would prefer to leave this as-is and instead spend the time on the real problem instead 😅 We can obviously document stuff, but I prefer docs that "just work".

@lfrancke

lfrancke commented Nov 20, 2026 •

Copy link
Copy Markdown
Member

@sbernauer Yes. And we're talking about how to fix that as well.
It's a bigger issue and you're welcome to join @labrenbe @siegfriedweber and me in the discussions. The results of which will end up in a decision anyway. Benedikt already wanted to start writing one.

On the Kafka end we can also see wheter/how we can improve things.

@lfrancke lfrancke moved this from Development: Waiting for Review to Development: In Review in Stackable Engineering Nov 20, 2026
@sbernauer

Copy link
Copy Markdown
Member

I mean the proper solution from my point of view is platformManaged (sadly not implemented yet), so the operator decides what is best (mTLS, token, static secret, whatnot) and we can non-breaking improve things over time there. Ideally we can update the "getting started" docs to that later anyway.

@labrenbe
labrenbe added this pull request to the merge queue Nov 20, 2026
Merged via the queue into main with commit d478323 Nov 20, 2026
11 checks passed
@labrenbe
labrenbe deleted the docs/add-management-access-warning branch November 20, 2026 09:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Development: In Review

Development

Successfully merging this pull request may close these issues.

3 participants