Expose Serving on Azure¶
This guide is under construction. We are working on fully supporting EKF on Azure in a later release.
This section will walk you through the steps required to expose the Serving Models of your cluster to the outside world. Specifically, you will use
- cert-manager to generate a self-signed certificate.
- NGINX Ingress Controller as an edge proxy exposed via an Azure Load Balancer.
- Istio behind NGINX Ingress Controller to expose the necessary Arrikto Enterprise Kubeflow workloads.
On most platforms, EKF supports both host-based and path-based serving. However, on Azure AKS you cannot use host-based serving because you will be using Azure’s DNS labels to get a DNS record for your load balancer, and as such, you cannot have a wildcard domain. For consistency, we will present both options in the following guides, but please use path-based serving.