docs (k8s): add Schema Registry ACLs for Redpanda Operator

[david-yu]

Summary

Do not Merge until 26.1 GA

Preview: https://deploy-preview-1619--redpanda-docs-preview.netlify.app/current/manage/kubernetes/security/authentication/k-schema-registry-acls/#grant-a-user-read-access-to-a-subject

• Adds a new page Manage Schema Registry ACLs (Operator) under Manage > Kubernetes > Security > Authentication and Authorization
• Documents the new subject and registry ACL resource types for User, RedpandaRole, and Group CRDs introduced in Add Schema Registry ACLs redpanda-operator#1306
• Adds nav entry and cross-links from the Schema Controller page
• Links to the existing Schema Registry Authorization page for concepts and supported operations

Test plan

• Verify the new page renders correctly in the Antora preview
• Verify nav entry appears under Security > Authentication and Authorization
• Verify cross-links from k-schema-controller page work
• Verify xref links to CRD reference and schema-reg-authorization resolve correctly
• Verify included example snippets from acceptance tests render properly (requires operator PR to be merged first for updated examples)

🤖 Generated with Claude Code

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 37a6ed6d-0545-466c-b8d0-853037044ac0

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

📝 Walkthrough

Walkthrough

This pull request adds documentation for managing Schema Registry ACLs with the Redpanda Operator in Kubernetes. The changes include a new navigation entry pointing to a comprehensive documentation file that describes how to define and manage Schema Registry ACLs across User, RedpandaRole, and Group resources. The documentation covers supported operations, prerequisites, manifest examples, common use cases, and verification steps. Additionally, cross-reference links are added to an existing schema controller documentation file.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• Update schema registry ACL details #1528 — Covers overlapping Schema Registry ACL operations and use cases, providing related content on supported operations and ACL examples.
• Improve authN and authZ topics #1115 — Modifies navigation and authentication-related documentation, addressing similar navigation structure updates.
• Add docs for the Role resource in Kubernetes #1378 — Updates documentation navigation and Kubernetes security/authentication pages with operator-managed ACL and role documentation.

Suggested reviewers

• sago2k8
• chrisseto
• Feediver1
• paulohtb6

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title clearly and concisely summarizes the main change: adding documentation for managing Schema Registry ACLs with the Redpanda Operator for Kubernetes.
Description check	✅ Passed	The PR description is comprehensive and well-structured, including summary, test plan, and Netlify preview link, covering all essential information for documentation changes.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[netlify]

✅ Deploy Preview for redpanda-docs-preview ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	d507904
🔍 Latest deploy log	https://app.netlify.com/projects/redpanda-docs-preview/deploys/69c6f68c0ba0fd00082c9a0b
😎 Deploy Preview	https://deploy-preview-1619--redpanda-docs-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

🧹 Nitpick comments (2)

modules/manage/pages/kubernetes/security/authentication/k-schema-registry-acls.adoc (1)

6-6: Prefer auto-title xrefs where possible.

Several xrefs hard-code link text; repository convention prefers xref:...[] so titles are pulled from targets automatically.

Based on learnings: "AsciiDoc linking: prefer using xref links with empty brackets (e.g., xref:section/target.adoc[]) because the title is pulled from the referenced document automatically."

Also applies to: 41-42, 55-56

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@modules/manage/pages/kubernetes/security/authentication/k-schema-registry-acls.adoc`
at line 6, The xref links in k-schema-registry-acls.adoc currently include
hard-coded link text (e.g.,
xref:reference:k-crd.adoc#k8s-api-github-com-redpanda-data-redpanda-operator-operator-api-redpanda-v1alpha2-user[User]
and
xref:reference:k-crd.adoc#k8s-api-github-com-redpanda-data-redpanda-operator-operator-api-redpanda-v1alpha2-role[RedpandaRole]);
replace those explicit labels with auto-title xrefs by removing the bracket text
so they become
xref:reference:k-crd.adoc#k8s-api-github-com-redpanda-data-redpanda-operator-operator-api-redpanda-v1alpha2-user[]
and
xref:reference:k-crd.adoc#k8s-api-github-com-redpanda-data-redpanda-operator-operator-api-redpanda-v1alpha2-role[],
and apply the same change to the other occurrences noted around lines 41-42 and
55-56 so the link titles are pulled automatically from the target documents.

modules/manage/pages/kubernetes/k-schema-controller.adoc (1)

281-281: Use empty-bracket xref for consistency with docs linking style.

This link can rely on target page title instead of hard-coded text.

Suggested diff

-* xref:manage:kubernetes/security/authentication/k-schema-registry-acls.adoc[Manage Schema Registry ACLs (Operator)]
+* xref:manage:kubernetes/security/authentication/k-schema-registry-acls.adoc[]

Based on learnings: "AsciiDoc linking: prefer using xref links with empty brackets (e.g., xref:section/target.adoc[]) because the title is pulled from the referenced document automatically."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@modules/manage/pages/kubernetes/k-schema-controller.adoc` at line 281,
Replace the explicit link text
xref:manage:kubernetes/security/authentication/k-schema-registry-acls.adoc[Manage
Schema Registry ACLs (Operator)] with an empty-bracket xref so the target title
is pulled automatically, e.g.
xref:manage:kubernetes/security/authentication/k-schema-registry-acls.adoc[];
update the occurrence in k-schema-controller.adoc where that xref appears.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@modules/manage/pages/kubernetes/k-schema-controller.adoc`:
- Line 281: Replace the explicit link text
xref:manage:kubernetes/security/authentication/k-schema-registry-acls.adoc[Manage
Schema Registry ACLs (Operator)] with an empty-bracket xref so the target title
is pulled automatically, e.g.
xref:manage:kubernetes/security/authentication/k-schema-registry-acls.adoc[];
update the occurrence in k-schema-controller.adoc where that xref appears.

In
`@modules/manage/pages/kubernetes/security/authentication/k-schema-registry-acls.adoc`:
- Line 6: The xref links in k-schema-registry-acls.adoc currently include
hard-coded link text (e.g.,
xref:reference:k-crd.adoc#k8s-api-github-com-redpanda-data-redpanda-operator-operator-api-redpanda-v1alpha2-user[User]
and
xref:reference:k-crd.adoc#k8s-api-github-com-redpanda-data-redpanda-operator-operator-api-redpanda-v1alpha2-role[RedpandaRole]);
replace those explicit labels with auto-title xrefs by removing the bracket text
so they become
xref:reference:k-crd.adoc#k8s-api-github-com-redpanda-data-redpanda-operator-operator-api-redpanda-v1alpha2-user[]
and
xref:reference:k-crd.adoc#k8s-api-github-com-redpanda-data-redpanda-operator-operator-api-redpanda-v1alpha2-role[],
and apply the same change to the other occurrences noted around lines 41-42 and
55-56 so the link titles are pulled automatically from the target documents.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 85b3a6ad-76ca-41ed-af12-72b7c75648f6

📥 Commits

Reviewing files that changed from the base of the PR and between 49e7aa6 and 85a8e11.

📒 Files selected for processing (3)

• modules/ROOT/nav.adoc
• modules/manage/pages/kubernetes/k-schema-controller.adoc
• modules/manage/pages/kubernetes/security/authentication/k-schema-registry-acls.adoc

[kbatuigas]

Thanks, @david-yu ! Please see comments on resolving build errors and rendering errors in code blocks.

[david-yu]

Thanks @kbatuigas I will incorporate your feedback.