This message was deleted.
# harvestera
adamant-kite-43734
06/28/2023, 8:18 PMThis message was deleted.
b
blue-kitchen-51801
06/28/2023, 8:21 PMI assume that there are some iptable rules configured to route the traffic from these ports to VIP Management ip
g
great-bear-19718
06/29/2023, 12:47 AMall nodes are listening on 80/443 because of the ingress controller
great-bear-19718
06/29/2023, 12:48 AMvip provides another way of accessing via a fixed address which is not tied to underlying nodes
b
blue-kitchen-51801
06/29/2023, 10:18 AMI’ve updated ingress-expose Loadbalancer service to expose on ports 8080 and 8443 but the change is affecting only the VIP not the other interfaces
blue-kitchen-51801
06/29/2023, 10:19 AMthat’s why I was thinking that there is another mechanism to serve Harvester UI on all interfaces
g
great-bear-19718
06/30/2023, 2:02 AMwell the vip is for service type loadbalancer.. and it points to ingress..
great-bear-19718
06/30/2023, 2:03 AMingress is also exposed as a daemonset on ports 443/80
🙌 1
👍 1
great-bear-19718
06/30/2023, 2:03 AMif you wish to disable this.. change will need to be to the ingress ds
great-bear-19718
06/30/2023, 2:03 AMplease be aware the change will likely be reset on upgrades
great-bear-19718
06/30/2023, 2:04 AM Copy code
ports:
- containerPort: 80
hostPort: 80
name: http
protocol: TCP
- containerPort: 443
hostPort: 443
name: https
protocol: TCP
- containerPort: 8444
name: webhook
protocol: TCP
readinessProbe:
failureThreshold: 3
httpGet:
path: /healthz
port: 10254
scheme: HTTP
initialDelaySeconds: 10
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 1
resources:
requests:
cpu: 100m
memory: 90Mi
securityContext:
allowPrivilegeEscalation: true
capabilities:
add:
- NET_BIND_SERVICE
drop:
- ALL
runAsUser: 101rke2-ingress-nginx-controllerkube-system👍 1
b
blue-kitchen-51801
06/30/2023, 3:57 AMthank you very much 👍👍
15 Views