-
Notifications
You must be signed in to change notification settings - Fork 70
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
Add network best practice document #429
base: main
Are you sure you want to change the base?
Conversation
76bc618
to
398e42b
Compare
✅ Deploy Preview for harvester-preview ready!
|
398e42b
to
6f26b5a
Compare
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.
Only some nits.
1fa7381
to
d8884ac
Compare
d8884ac
to
4044bcc
Compare
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!
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.
Small NITs. LGTM, thanks!
the best practice only covers what is needed from the routing/switching end. Though this is a good reference we should ideally leave it up to the end users. would it make sense to also have more info on how to configure cluster networks for different interfaces, and then created the VM networks? Some sample |
Good suggestion. I would add some reference cases about cluster networks and VM networks. |
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.
It is great to have such documents. Besides the current wonderful commit, also some suggestions:
There are a few traditional network setting scenarios in Harvester:
(1) All flat network, no isolation (home lab /trial)
(2) All vlan network, even for management, dedicated nics (production deployment)
(3) Mixed un-tagged and tagged network; only 1 nic (home lab /trial/poc...)
(4) Mixed un-tagged and tagged network; multi nics (poc ...)
This doc covers (4); we may also list (1)~(3) and update them now or future. thanks.
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. thanks.
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, thanks.
@w13915984028 Can you help finalize this PR by creating pages in https://github.com/harvester/docs/tree/main/versioned_docs/version-v1.2 as well? I guess at the writing time, the v1.2 was not released yet. |
This is not part of this PR but in deep-dive.md, line 110, there is a typo, where any chance we can please fix this too? |
Signed-off-by: yaocw2020 <[email protected]> Co-authored-by: vickyhella <[email protected]>
Co-authored-by: Lucas Saintarbor <[email protected]>
f7eb86c
to
bff2239
Compare
Signed-off-by: Jian Wang <[email protected]>
bff2239
to
901f960
Compare
@bk201 This PR is ready for final merging now. Thanks again for @yaocw2020 's great effort. |
No description provided.