https://rancher.com/ logo
#rke2
Title
# rke2
a

adamant-kite-43734

02/08/2023, 2:30 PM
This message was deleted.
a

agreeable-oil-87482

02/08/2023, 3:15 PM
I believe it was changed at one point, but currently it's configured as such to mimic how the built in ingress controller in RKE1 operates, which is also partly for ease.
a

abundant-noon-17295

02/08/2023, 3:27 PM
i thought it might be due to some nodePort svc drawbacks, thanks David.
r

refined-analyst-8898

03/27/2023, 3:35 AM
I created an RKE2 cluster w/ Harvester Cloud Provider and encountered this too. For me the solution was a LoadBalancer service selecting the daemonset's pods. I created a vip-pool in the Harvester node to supply an external IP for the service.
Copy code
apiVersion: v1
kind: Service
metadata:
  name: ingress-nginx-loadbalancer
spec:
  selector:
    <http://app.kubernetes.io/name|app.kubernetes.io/name>: rke2-ingress-nginx
  ports:
    - protocol: TCP
      port: 80
      targetPort: 80
      name: http
    - protocol: TCP
      port: 443
      targetPort: 443
      name: https
  type: LoadBalancer
21 Views