Expose Serving on Google Cloud

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

  • NGINX Ingress Controller as an edge proxy exposed via a Google Cloud Load Balancer.
  • Cloud DNS to create a managed zone for your domain.
  • ExternalDNS to create dynamic DNS entries for your domain.
  • cert-manager to handle SSL certificates.
  • Istio behind NGINX Ingress Controller to expose the necessary Arrikto Enterprise Kubeflow workloads.


We recommend that you use path-based serving for exposing your served models to the outside world. In particular, you cannot use host-based serving if you use Let’s Encrypt for your SSL certificates, or Cloud Endpoints for your DNS record. For these cases use path-based serving instead.