Skip to content
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

Harvester - Quickstart using management cluster network #237

Open
ProtossGP32 opened this issue Aug 2, 2024 · 0 comments
Open

Harvester - Quickstart using management cluster network #237

ProtossGP32 opened this issue Aug 2, 2024 · 0 comments

Comments

@ProtossGP32
Copy link

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:

imatge

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:

imatge
imatge

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 a network-attachment-definition:
imatge

kubectl --kubeconfig ~/.harvester/config get network-attachment-definitions.k8s.cni.cncf.io -A
NAMESPACE   NAME       AGE
default     untagged   117m
default     vm-net-1   3h13m
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant