Installing Ingress Controller

Install the NGINX Ingress Controller which manages external HTTP/HTTPS access to the services in a cluster.

About this task

  • Required for the Orient Me and Customizer offerings. Also, can be used to access the Sanity dashboard.
  • The NGINX Server runs on its own static ports:
    • HTTP: 32080
    • HTTPS: 32443
  • Traffic routing is controlled by rules defined on the ingress resource.
  • The following ingress rules are included by default:
    • Access the sanity dashboard through Ingress at the following URL: http://<master_node>:32080/sanity/. For high availability deployments, replace <master_node> with the load balancer DNS of the HA cluster.
    • Access the following Orient Me applications though Ingress: orient-web-client, itm-services, community-suggestions, appregistry-service and appregistry-client. That will mean that when updating the IBM HTTP server configuration with the proxy pass rules for Orient Me, you will use the same port for all of the entries, refer to Configuring the HTTP server for Orient Me for additional information.
  • Custom rules can be applied once cnx-ingress is running. Ingress Rules.


  1. Install the cnx-ingress Helm chart by running the following command:
    Note: By default, deployment is done to the connections namespace. If you created a namespace with a different name and would like to deploy there, the following extra value must be included in the helm install command: namespace=namespace.
    domain_name=`hostname -d`
    helm install \
    --name=cnx-ingress extractedFolder/microservices_connections/hybridcloud/helmbuilds/cnx-ingress-0.1.0-20190918-222428.tgz
    --set \
    In the command, replace extractedFolder with the location of the directory where you extracted the Component Pack installation package. Replace the value of image.repository with the name of your Docker registry
  2. Verify the install of the cnx-ingress:
    1. Verify that the installation completed by running the helm list command. When the installation completes, the chart's status shows as DEPLOYED.
    2. Then run the following command to check the status of all of the pods.
      kubectl get pods -n connections