This message was deleted.

how are you upgrading? And are you talking about rke2 on VMs? sounds like it is an rke2 issue and not harvester.

Finally, I've managed to fix the issue. It was caused by Calico using the Harvester VIP LoadBalancer IP instead of the node interface. It would be good to implement a proper fix in Rancher or Harvester so that people won't encounter this problem when using LoadBalancers from Harvester. More details below: https://github.com/rancher/rke2/issues/8477#issuecomment-3024283591

interesting.

Most likely other people don't have this problem because they don't set up nginx ingress to expose it on Harvester Loadbalancer.

apiVersion: <http://helm.cattle.io/v1|helm.cattle.io/v1>
kind: HelmChartConfig
metadata:
  name: rke2-ingress-nginx
  namespace: kube-system
spec:
  valuesContent: |-
    controller:
      kind: Deployment
      replicaCount: 3
      ingressClassResource:
        enabled: 'true'
        default: 'true'
        name: nginx
      ingressClassByName: 'true'
      publishService:
        enabled: true
      hostPort:
        enabled: false
      service:
        enabled: true
        type: LoadBalancer
        annotations:
          <http://cloudprovider.harvesterhci.io/ipam|cloudprovider.harvesterhci.io/ipam>: "dhcp"

I had the same problem with rke2 v1.31.8 which was my first try and thought that it just wouldn't work at all. Good to know that it should work with v1.31.4 and will give that a try tomorrow