-
Notifications
You must be signed in to change notification settings - Fork 14.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
node: start moving the resource management docs to concepts #48797
node: start moving the resource management docs to concepts #48797
Conversation
👷 Deploy Preview for kubernetes-io-vnext-staging processing.
|
dbdd3ec
to
84d616d
Compare
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
Totally agree to this refactoring, however, I'd suggest we postpone this because 1.32 is about to be released soon. Propagating this change to localization teams takes some time. |
If this helps, what I want to do here is 90% content movement (which I honestly believe helps anyway). @sftim could you please provide your take here about @tengqm 's concern, also considering #48797 (comment) ? |
The decision is about what to postpone
In an ideal world, we avoid adding features where we don't also have capacity to document them well. That's what commercial product docs often aim for. In the same ideal world, we planned in that refactoring early. See #48340 (comment) for a compromise option. How does that sound? |
If we can get the refactoring done within a few days of now, I'd prefer to land it and redo the feature PRs. |
ok, fair point. Let's timebox this attempt. I'll need some sig-node reviews and I asked for them: https://kubernetes.slack.com/archives/C0BP8PW9G/p1732284959539839 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
content/en/docs/tasks/administer-cluster/cpu-management-policies.md
Outdated
Show resolved
Hide resolved
content/en/docs/tasks/administer-cluster/cpu-management-policies.md
Outdated
Show resolved
Hide resolved
LGTM label has been added. Git tree hash: df88e29f6338dc3d61435521fba556715bf73816
|
thanks @sftim ! I'm adopting all your suggestions |
84d616d
to
a8423dd
Compare
We have reached a point where the existing CPU management task page is quite hard to follow. Start moving the resource management concepts to the concept page. We begin with the CPU management policies, the worst offender right now. Over time, the plan is to move all the concepts from tasks in the concepts page. Signed-off-by: Francesco Romani <fromani@redhat.com>
a8423dd
to
96a2e17
Compare
/label refactor |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Informal LGTM
/approve
Ready for LGTM
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sftim 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 |
/lgtm |
LGTM label has been added. Git tree hash: 3dc8f3cd22192f0a110f9017cbad3dfe2459bc09
|
Description
Move the cpu management policies and options docs from tasks to concepts
xref: #48340 (review)
In the 1.32 cycle I don't have capacity to move except for CPU manager, which is the worst offender anyway. Other managers should follow suite, hopefully in the 1.33 cycle already.
Issue
Closes: #38121 (albeit in a different and IMO better way)