update components-permission docs #728
Merged
Conversation
This file contains 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
karmada-bot
added
the
kind/feature
karmada-bot
added
the
size/XS
windsonsea
reviewed
Nov 8, 2024
karmada-bot
added
size/L
|
cc @RainbowMango I have revised the content and layout of the component-permission |
zhzhuang-zju
force-pushed
the
rbac
branch
2 times, most recently
from
f3f1c44 to
697929c
Compare
i18n/zh/docusaurus-plugin-content-docs/current/administrator/security/component-permission.md
Outdated
Show resolved
Hide resolved
i18n/zh/docusaurus-plugin-content-docs/current/administrator/security/component-permission.md
Outdated
Show resolved
Hide resolved
i18n/zh/docusaurus-plugin-content-docs/current/administrator/security/component-permission.md
Outdated
Show resolved
Hide resolved
|
|
||
| # Karmada Component Permissions | ||
|
|
||
| As a multi-cluster management framework, it is crucial to control the permissions of Karmada components based on the resources they access to maintain the security and stability of the entire system. The Karmada community has compiled a list of resources that key components require access to and has implemented the principle of least privilege for the relevant components using the community-maintained installation and deployment tool. This document aims to outline the list of resources that Karmada components need to access along with the reasons for accessing those resources, providing clear guidance for users customizing component permissions. |
There was a problem hiding this comment.
Suggested change
| As a multi-cluster management framework, it is crucial to control the permissions of Karmada components based on the resources they access to maintain the security and stability of the entire system. The Karmada community has compiled a list of resources that key components require access to and has implemented the principle of least privilege for the relevant components using the community-maintained installation and deployment tool. This document aims to outline the list of resources that Karmada components need to access along with the reasons for accessing those resources, providing clear guidance for users customizing component permissions. | |
| This document provides a detailed explanation of the resources each Karmada component needs to access and the reasons for these accesses. It will help administrators understand and configure the RBAC permissions needed for Karmada components effectively, ensuring that the system operates securely and efficiently. | |
| The [installation tools](https://karmada.io/docs/installation/) maintained by the community are designed with security in mind. These tools use Role-Based Access Control ([RBAC](https://kubernetes.io/docs/reference/access-authn-authz/rbac/)) to manage access to components, ensuring they only have access to the resources they require. By adhering to the principle of least privilege, these tools minimize potential security risks and prevent unauthorized access or actions within the system. |
Signed-off-by: zhzhuang-zju <[email protected]>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: RainbowMango The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
karmada-bot
added
the
approved
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.
What type of PR is this?
/kind feature
What this PR does / why we need it:
Further reduce the permissions of karmada-agent
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer: