KEP-4322: Fix terminology inconsistency by replacing "management cluster" with "hub cluster"#5724
Conversation
…ter" with "hub cluster" Signed-off-by: kahirokunn <okinakahiro@gmail.com>
|
Hi @kahirokunn. Thanks for your PR. I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
Hi @corentone, I noticed a terminology inconsistency in the "Pull Model with Work API" section where "management cluster" was used instead of "hub cluster". This PR fixes those two instances to maintain consistency throughout the KEP document. Could you please review this change when you have a chance? Thank you! |
|
/lgtm Thank you for cleaning up! |
|
/approve Thanks! |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kahirokunn, lauralorenz, skitt The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
KEP-4322: Fix terminology inconsistency by replacing "management cluster" with "hub cluster"
One-line PR description: Fix terminology inconsistency in the Pull Model with Work API section
Other comments:
This PR fixes terminology inconsistency found in the "Pull Model with Work API" section.
The document consistently uses "hub cluster" throughout, but there were two instances
where "management cluster" was used instead. This change ensures consistent terminology
across the entire KEP document.