user-guide
user-guide copied to clipboard
NUMA.md add Additional Reading section
What this PR does / why we need it:
Add 'Additional Reading' section to the NUMA page to mention related Kubernetes topics.
Which issue(s) this PR fixes
Fixes #755
Special notes for your reviewer:
Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR. Approvers are expected to review this list.
- [ ] Design: A design document was considered and is present (link) or not required
- [ ] PR: The PR description is expressive enough and will help future contributors
- [ ] Code: Write code that humans can understand and Keep it simple
- [ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
- [ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
- [ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
- [ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
- [ ] Community: Announcement to kubevirt-dev was considered
Release note:
NONE
Hi @ianb-mp. Thanks for your PR.
I'm waiting for a kubevirt member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
Instructions 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/test-infra repository.
@xpivarc @acardace is this something you can help with?
@phoracek @stu-gott please review
Not an expert in real-time and NUMA but looks good to me.
/lgtm /approve
according to Antonio's comment
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: fabiand
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [fabiand]
Approvers can indicate their approval by writing /approve
in a comment
Approvers can cancel approval by writing /approve cancel
in a comment
+1