Deploy two instances of an ingress controller:
-
The external instance:
-
Must use an external load balancer.
-
Will be used as an incoming APS proxy to provide external access to the APS REST API.
-
-
The internal instance:
-
Must use an internal load balancer.
-
Will be used to provide internal access to the CloudBlue Commerce control panels and the UIs of the monitoring and alerting solution.
-
When deploying these instances, take the following into account:
-
You can use the NGINX Ingress Controller.
-
You must deploy the components of an ingress controller in the namespace that you prepared for infrastructure components.
-
Different instances of an ingress controller must belong to different ingress classes.
-
The internal instance must be configured to use an internal load balancer.
To learn how to deploy an ingress controller, please refer to the Kubernetes documentation and the documentation of the ingress controller that you are going to deploy.
Note: Deploying the internal instance of an ingress controller is optional but recommended.