This message was deleted.
# harvestera
adamant-kite-43734
05/09/2024, 7:23 PMThis message was deleted.
b
bland-article-62755
05/10/2024, 4:47 AMCan you verify the traffic from inside the VMs? Maybe VM networking is broken somehow?
r
rhythmic-article-81903
05/10/2024, 8:39 AMThat is exactly what I did. Everything else works from VM but not VIP https (https to all harvester nodes for example). VIP https works from harvester nodes and I can see that firewall passes traffic without issues. To me it seems that VIP just doesn't respond to request.
b
bland-article-62755
05/10/2024, 2:04 PMAre they all in the same subnet and route?
r
rhythmic-article-81903
05/12/2024, 9:42 PMit is this same issue https://github.com/harvester/harvester/issues/3448
b
bland-article-62755
05/13/2024, 12:54 AMCan you post the yaml from the
rancher-exposecattle-systembland-article-62755
05/13/2024, 12:54 AMIt should be the output from
kubectl get ingress/rancher-expose -n cattle-system -o yamlbland-article-62755
05/13/2024, 12:56 AMI've only had this happen after setting a dns name on the route there and I assumed it was actually the security failing because of the new cert.
r
rhythmic-article-81903
05/13/2024, 8:49 AMI can create cluster when I point rancher dns name to node and not VIP. This is clearly problem with VIP. It only works properly outside of the cluster and when traffic originates from inside the cluster (inside mgmt network)... no luck
b
bland-article-62755
05/13/2024, 2:27 PMwell good luck then ¯\_(ツ)_/¯
19 Views