Clarify control plane node description in cluster introduction#56522
Clarify control plane node description in cluster introduction#56522Debasish-87 wants to merge 1 commit into
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
lmktfy
left a comment
There was a problem hiding this comment.
Thanks for the PR. Superficially it looks consistent, but there's a problem. People reading this may get an idea about Kubernetes and its control plane that is unhelpfully misleading.
It's a subtle detail but that perhaps makes it all the more important not to teach it wrongly.
|
Thanks for the detailed explanation. I understand the concern now. I based my change on the wording suggested in the linked issue, but I agree that it shouldn't imply control plane nodes are required for all Kubernetes clusters. I'll revise the PR to keep the tutorial accurate while still addressing the original confusion. |
cc7312a to
3a1cad8
Compare
|
Thanks again for the feedback. I've updated the wording to avoid implying that control plane nodes are required and simplified the paragraph to describe a common supported deployment model. Please let me know if you'd like me to adjust the wording further. |
Fixes #56507
What this PR does