This message was deleted.
# harvester
a
This message was deleted.
b
The best thing to do is to create layer 2 VM networks (vlans) and tie those to your virtual machines. Other option if you want your server to continue doing nat and/or routing for some reason, you could setup load balances, potentially.
i
Hello Mike, thanks for the directions. I assume vlan allows just communication between VMs, right? I would like to make different services available. As a matter of principle I would like to make a webserver, nextcloud, nextcloud talk, gitlab and the gitlab registry available on the VIP of the harvester cluster (hence also ports except https). In the meantime I assume the right way to go is this plugin https://docs.harvesterhci.io/v1.2/advanced/addons/rancher-vcluster/ Seems just one thing missing. I would like to add cert-manager into the game. Currently still looking for a tutorial on how to set these things up
For the non https ports, is there some kind of construct like a NodePort for the VMs? And maybe another more general question. I would like to do the configruations in a kind of gitOps way. Is this currently possible with harvester and are you maybe aware of some tutorial kind information in this regards?
w
The VIP is specific to Harvester, you can't add additional services to that IP address.
i
Hello Simon, I just had a look into https://docs.harvesterhci.io/v1.2/advanced/addons/rancher-vcluster seems like it syncs the ingress with the IP. Are you sure about this?
"it says "During the installation, the ingress for Rancher is synced to the Harvester cluster, allowing end users to access Rancher." My hope therefore was that I could use the ingress of the rancher-vluster to get certs with lets-encrypt and provide an interface to my services. So the way you are seeing for it, would be, to require an external Rancher which than makes all Harvester services available? I do not want to spent money on an extra server to make this possible.
b
Vlans are what you are looing for. They are not just for inter vm communication. Put yourself a router or a firewall attached to your switch that your servers is connected to. Create a vlan say vlan 100, put your layer 3 ip info on it, and extend that vlan to your VM by creating a layer 2 vlan in harvester.
i
Hello Mike, I have my server standing at a Hetzner datacenter. Not sure how this should work. They allow me to create a vlan and to connect it with my hosts. HOwever, I cannot set any other options their. When installing harvester with vlan enabled, I did not get internet connectivity in the installer. I therfore disabled it. My assumption is that the vlans I can set up their are only thought to be used for internal traffic routing. So if I understand you correctly I would have to map the vlan to a dns record? How is this normally done?
I map a vlan to an IP via router configuration and set a DNS record on it?
@witty-jelly-95845 Hello, with the new rancher-vcluster plugin I assume it will be possible to at least make http and https visible to the outside. Unfortunately, I still have not found out about the approach you recommended to use vlans for it. Could you maybe provide some more detail on how this should work? https://github.com/harvester/experimental-addons/issues/5#issuecomment-1757949065
w
The VIP address is for Harvester (and Rancher vcluster) access, not for any other services.
b
You need to create some vlans and tag them on a router in front of your cluster, then tag those to your vms. What you are trying to do is more similar to kubernetes infrastructure, but this is HCI and is not going to work the way you want. You could easily turn up a router or some load balancers or both on your harvester cluster, then use that to do what you want and provide front end services etc.
Just my thoughts
r
Is there a way to bootstrap the management node with a DNS SAN on the VIP's server certificate? I entered the IP when the installer prompted for the VIP, and didn't try entering a domain name at that point in the process. I'm looking to use the VIP's domain name to add nodes, if possible, but the server certificate has only the IP SAN, so nodes are unable to verify the server certificate during enrollment and get stuck forever on NotReady.