Repository navigation
[DOCS#EV-7496]: Manage Team permissions for endpoints, Prometheus charts and log roles - #3191
Draft
dimitri-nicolo wants to merge 2 commits into
Draft
dimitri-nicolo wants to merge 2 commits into
dimitri-nicolo wants to merge 2 commits into
Conversation
…log roles in Manage Team Also name the current queryserver proxy in the example UI roles, keeping the pre-3.22 name for older releases.
✅ Deploy Preview for calico-docs-preview-next ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview succeeded!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues are identified, and the documentation and RBAC updates address the intended permission scope and current and legacy API proxy names.
No open issues 🎉
What changed in this PR
Updates Calico Enterprise documentation and sample RBAC manifests to clarify Manage Team permission scope and support the current calico-api proxy service name while retaining legacy compatibility.
Changes:
- Documents cluster-wide visibility for dashboards, Service Graph, logs, and endpoints.
- Explains Prometheus-backed traffic chart access and required permissions.
- Adds
https:calico-api:8080to both RBAC examples while preservinghttps:tigera-api:8080.
| File | Description |
|---|---|
static/files/read-all-crud-default-rbac.yaml |
Supports current and legacy Calico API proxy service names. |
static/files/min-ui-user-rbac.yaml |
Supports current and legacy Calico API proxy service names for minimal UI access. |
calico-enterprise/operations/cnx/manage-roles.mdx |
Documents Manage Team permission scope, endpoint access, and Prometheus chart requirements. |
This pull request is ready to be approved.
Review effort: Lite
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
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.
Product Version(s):
Calico Enterprise, next release (Manage Team is unreleased; the proxy-name fix in the example roles applies to every version).
Issue:
EV-7496 (tigera/calico-private#15234), EV-7497 (tigera/calico-private#15222) and EV-7499 (tigera/calico-private#15224). Merge after all three.
Link to docs preview:
calico-enterprise/next/operations/cnx/manage-roles#what-some-permissions-include
SME review:
DOCS review:
Additional information:
tigera-intrusion-detection, through its own RoleBinding there, which the page now lists and which an export carries (#15224).min-ui-user-rbac.yamlandread-all-crud-default-rbac.yamlgranted the queryserver proxy ashttps:tigera-api:8080, which nothing has checked since v3.22. They now namehttps:calico-api:8080as well. The old name stays because the 3.21 docs use the same files.This PR was written in part with the assistance of generative AI (Claude Code).
Merge checklist: