Add Confluent Platform RBAC guidance to Kafka ACL setup - #38664
Draft
piochelepiotr wants to merge 2 commits into
Draft
Add Confluent Platform RBAC guidance to Kafka ACL setup#38664piochelepiotr wants to merge 2 commits into
piochelepiotr wants to merge 2 commits into
Conversation
…or Kafka setup Customers running self-hosted Confluent Platform with RBAC instead of native Kafka ACLs had no guidance on which role bindings the Datadog Agent principal needs.
Remove the CLI example and rationale prose per feedback; scope DeveloperRead to all topics/groups instead of naming specific resources.
Contributor
Preview links (active after the
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Splits the "ACL permissions" section of the Kafka Monitoring setup page into two tabs — ACLs and Confluent Platform roles — so self-hosted Confluent Platform customers using RBAC (instead of native Kafka ACLs) have explicit guidance on which role bindings (
Operatoron the cluster,DeveloperReadon topics/groups) to grant the Datadog Agent principal, including exampleconfluent iam rbac role-binding createcommands. Also clarifies that the message-inspection "Additional ACL permission" section doesn't require an extra RBAC binding, sinceDeveloperReadalready includesRead.Prompted by a support case (Zendesk #2964638) where a Confluent Platform RBAC customer asked whether ACL requirements differ under RBAC.
Merge readiness
For Datadog employees:
<name>/<description>convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR./reviewto run an automated check that catches common issues before a Documentation team member reviews your PR.AI assistance
Drafted with Claude Code based on Slack thread discussion and a read of the
kafka_consumerintegration's admin-client calls inintegrations-core; not yet reviewed by a Confluent RBAC subject-matter expert.Additional notes
The exact RBAC role-to-operation mapping (
Operator+DeveloperRead) is based on Confluent's documented predefined roles and the Kafka Agent'sdescribe_cluster/describe_consumer_groups/list_consumer_group_offsetscalls, but has not been validated against a live Confluent RBAC cluster. Please have someone with hands-on Confluent RBAC experience confirm before merging.