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.
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
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
- If you don’t have a TCP service configmap then create a new one and update the ingress controller args:
Next, update the port in ingress controller deployment/daemonset and in ingress controller service.
Changes in deployment/daemonset:
- containerPort: 13443
Changes in service:
- name: 13443-tcp
Disable Deepfactor Portal Ingress
Finally, customize the Deepfactor portal to disable its internal ingress. Here is a sample
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).