Skip to content

Fix formatting for overlay NIC instructions #1047

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.

Sign up for GitHub

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

Open
allexistence wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix formatting for overlay NIC instructions #1047

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions versioned_docs/version-v1.8/networking/harvester-network.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -162,7 +162,7 @@ When you change the network type from `VLAN` to `VLAN Trunk` or `Untagged`, the

:::

## Overlay Network (Experimental)
## Overlay Network (Experimental)

_Available as of v1.6.0_

Expand Down Expand Up @@ -212,7 +212,7 @@ The overlay network implementation in Harvester v1.6 has the following limitatio

- The static IP in cloud-init appears to be ignored for overlay NICs. In practice, the static IP works *only if it matches the exact address Kube-OVN has reserved* for the virtual machine. Any other value breaks connectivity.

- When multiple NICs are attached and the overlay NIC is not the primary interface, you must manually initialize the overlay NIC within the guest operating system (IP link setup) and run the DHCP client (dhclient) command to obtain the NIC's IP address.
- When multiple NICs are attached and the overlay NIC is not the primary interface, you must manually initialize the overlay NIC within the guest operating system (`ip link`) and run the DHCP client (`dhclient`) command to obtain the NIC's IP address.

- Peering only works between custom VPCs. Attempts to establish a peering connection between the default VPC and a custom VPC will fail.

Expand Down