Connect the ICAP Client outside K8s to ICAP on K8s

  1. MetaDefender ICAP Server has already deploy to K8S environment by MetaDefender ICAP Server helm (refer to: $link[page,369806,auto$])

Option 1: using NGINX Ingress

Setup Metallb:

  1. Clone metallb
  2. update helm-bitnami/bitnami/metallb/values.yaml
  1. install helm chart
  1. make sure metallb is running

Setup NGINX ingress:

  1. get ingress-nginx
  1. append below to values.yml
  1. Helm install Nginx-ingress
  1. Create file ingress.yml as below:
  1. Create ingress resources on Kubernetes
  1. Verify Metallb assign IP address external to Nginx-ingress

Option 2: Using NodePort

  1. Update field service_type from ClusterIP to NodePort in values.yaml of ICAP helm and save to file update_nodeport_values.yml
  1. Update config
  1. make sure pod MetaDefender ICAP Server is running

For example: this case md-icapsrv-5df4bb8547-czp88 is running

  1. Get service port with CLI

For example: the service port mapping ressult:

  • 8048:31988/TCP
  • 1344:32233/TCP
  • 11344:32568/TCP
  1. Check the MetaDefender ICAP Server is running on the worker node
  1. Describe pod md-icapsrv-5df4bb8547-czp88 to get the IP address
  1. ICAP Client will connect to MetaDefender ICAP Server via below IP and Port
Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard
On This Page