Deepfactor portal employs a LoadBalancer service for Ingress by default, which comes with its own helm chart. A LoadBalancer is typically provided by different cloud providers to assign IPs to the Ingress service.
However, LoadBalancer may not be present in bare metal clusters, causing the Ingress service to be stuck in pending state. In order to access the Deepfactor portal in such environments, the user can specify External IPs which would be the node’s private or public ip.
In order to configure the ExternalIPs, please add the following section to override.yaml before passing it as an option to helm install/upgrade command
ingress-nginx:
controller:
service:
externalIPs:
- IP1
- IP2
IP1 and IP2 can be the external IP or node public/private IP
Network Diagram for communication using Node IP
