If you have multiple Kubernetes clusters, you can switch to another cluster to deploy, for example:
After a while, you can see the public IP of the tf-hub-lb service, which is the access address for JupyterHub:
For clusters that do not support LoadBalancer Service, you can also access it through port forwarding (http://127.0.0.1:8100):
By default, JupyterHub can be logged in with any username and password. After logging in, you can use custom images to start the Notebook Server, such as:
Kubeflow: Google's Kubernetes-Based Framework for Managing TensorFlow Tasks
Kubeflow, crafted by Google, is an exceptional tool for deploying and overseeing TensorFlow processes within Kubernetes environments. It boasts a suite of impressive features, such as:
JupyterHub services for the seamless running of Jupyter notebooks
A dedicated Tensorflow Training Controller for orchestrating training operations
A ready-to-serve TF Serving container aimed at model deployment
How to Deploy
Before ushering into the deployment phase, ensure the following prerequisites are met:
An operational Kubernetes cluster or Minikube, along with the adeptly configured kubectl CLI
Installation of ksonnet version 0.8.0 or higher is complete
In the case of Kubernetes clusters that are fortified with RBAC, kick off by assembling an admin-level cluster role binding:
Subsequently, embark on the deployment journey with these commands:
Got more than one Kubernetes cluster? No problem! Simply swap over to another and proceed with the deployment, take for instance:
Hang tight for a bit, and soon the tf-hub-lb service's public IP surfaces, serving as your gateway to JupyterHub:
In scenarios where the LoadBalancer Service isn't in the cards, reach your destination via port forwarding (http://127.0.0.1:8100):
JupyterHub's doors are open to any username and password by default. Once inside, spark up your Notebook Server using custom images like: