Installing Kubeflow 1.3+ on an Existing and Private GKE Cluster
Installing Kubeflow is not trivial, and is made even trickier given the myriad Kubernetes setups. In this article, I am going to show you how to set up Kubeflow 1.3 (this should even for later version of Kubeflow) on a Kubernetes cluster backed by Google Kubernetes Engine.
However, I’m going to take this up a notch: These instructions will apply to a private GKE cluster. Not only that, I’m not going to assume that you are installing this on a fresh, brand-new cluster.
When I started the journey of figuring out how to do this, the information available was sparse and often outdated. The official installation instructions to install Kubeflow on GKE also comes with a few drawbacks:
- Assumes that the cluster is going to be created from scratch
- Requires the creation of a management cluster
- Requires exposing a public IP address
- Lacks instructions to install Kubeflow on a private GKE cluster
- Doesn’t specify firewall rules
Updating Firewall Rules for Istio, Kubeflow, and KFServing
By default, firewall rules restrict your cluster control plane to only initiate TCP connections to your nodes and Pods on ports…
