Running the Deepfactor Portal With Existing Kubernetes Ingress Follow

The Deepfactor portal can be deployed behind existing ingress. As Deepfactor needs port 13443 to establish a TCP connection between the backend and portal, we need to expose this port through ingress. Here are the steps to configure this. For more info, please check the Kubernetes ingress doc.

Helm Installation

If you have installed or will install the NGINX Ingress Controller via its Helm chart, then you will need to add a value to the chart via override.yaml

tcp:
  13443: "deepfactor/deepfactor-nginx:13443"

Direct Installation

If you have installed or will install the NGINX Ingress Controller via yaml files, you need to update the  yaml files as outlined below:

• If you already have a TCP service configmap then update the configmap with the lines below inside data

• If you don’t have a TCP service configmap then create a new one and update the ingress controller args:

apiVersion: v1
  data:
   "13443": deepfactor/deepfactor-nginx:13443
kind: ConfigMap
metadata:
  name: ingress-nginx-tcp

Next, update the port in ingress controller deployment/daemonset and in ingress controller service.

Changes in deployment/daemonset:

- containerPort: 13443
   name: 13443-tcp
   protocol: TCP

Changes in service:

 - name: 13443-tcp
   nodePort: 31379
   port: 13443
   protocol: TCP
   targetPort: 13443-tcp

Disable Deepfactor Portal Ingress

Finally, customize the Deepfactor portal to disable its internal ingress. Here is a sample override.yaml:

ingress-nginx:
  enablemodule: false
nginx:
  ingress:
className: nginx

Deepfactor portal can be configured with a configurable TCP port (instead of 13443).  To enable this feature, visit Change default Web Scan TCP port (default 13443).