You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DESCRIPTION: I'd like to be able to deploy Rancher on Harvester by using the Management network as the VMs network.
RATIONALE: I've deployed Harvester 1.3.1 in a server that currently has only one enabled NIC. I'm having troubles properly configuring a VM network binded to the mgmt Cluster Network that assign IPs to the VMs (I don't have a DHCP server for this) and the only way I've been able to assign IPs to VMs is by selecting mgmt network as the primary VM network interface. Having reached that point, I'd expect the Terraform quickstart deployment to accept the mgmt Cluster network as a valid one even if no VM network are available:
You can see here that the quickstart VM is trying to use a VM network bridget to the mgmt Cluster Network but it isn't retrieving IPs:
Comparing the Network configs on the VMs I see that the ones with IP have a network_namemanagement Network, but I can't seem to be able to use it in the quickstart Terraform variable nor I find it as a network-attachment-definition:
kubectl --kubeconfig ~/.harvester/config get network-attachment-definitions.k8s.cni.cncf.io -A
NAMESPACE NAME AGE
default untagged 117m
default vm-net-1 3h13m
The text was updated successfully, but these errors were encountered:
DESCRIPTION: I'd like to be able to deploy Rancher on Harvester by using the Management network as the VMs network.
RATIONALE: I've deployed Harvester 1.3.1 in a server that currently has only one enabled NIC. I'm having troubles properly configuring a VM network binded to the
mgmt
Cluster Network that assign IPs to the VMs (I don't have a DHCP server for this) and the only way I've been able to assign IPs to VMs is by selectingmgmt
network as the primary VM network interface. Having reached that point, I'd expect the Terraform quickstart deployment to accept themgmt
Cluster network as a valid one even if no VM network are available:You can see here that the quickstart VM is trying to use a VM network bridget to the
mgmt
Cluster Network but it isn't retrieving IPs:Comparing the Network configs on the VMs I see that the ones with IP have a
network_name
management Network, but I can't seem to be able to use it in the quickstart Terraform variable nor I find it as anetwork-attachment-definition
:kubectl --kubeconfig ~/.harvester/config get network-attachment-definitions.k8s.cni.cncf.io -A NAMESPACE NAME AGE default untagged 117m default vm-net-1 3h13m
The text was updated successfully, but these errors were encountered: