This example guides you through the process of taking an example model, modifying it to run better within Kubeflow, and serving the resulting trained model.
Follow the version of the guide that is specific to how you have deployed Kubeflow
- MNIST on Kubeflow on GCP
- MNIST on Kubeflow on AWS
- MNIST on Kubeflow on Azure
- MNIST on Kubeflow on IBM Cloud
- MNIST on Kubeflow on vanilla k8s
Follow these instructions to run the MNIST tutorial on GCP
-
Follow the GCP instructions to deploy Kubeflow with IAP
-
Launch a Jupyter notebook
- The tutorial has been tested using the Jupyter Tensorflow 1.15 image
-
Launch a terminal in Jupyter and clone the kubeflow examples repo
git clone https://github.com/kubeflow/examples.git git_kubeflow-examples
-
Tip When you start a terminal in Jupyter, run the command
bash
to start a bash terminal which is much more friendly then the default shell -
Tip You can change the URL from '/tree' to '/lab' to switch to using Jupyterlab
-
-
Open the notebook
mnist/mnist_gcp.ipynb
-
Follow the notebook to train and deploy MNIST on Kubeflow
Follow these instructions to run the MNIST tutorial on AWS
-
Follow the AWS instructions to deploy Kubeflow on AWS
-
Launch a Jupyter notebook
- The tutorial has been tested using the Jupyter Tensorflow 1.15 image
-
Launch a terminal in Jupyter and clone the kubeflow examples repo
git clone https://github.com/kubeflow/examples.git git_kubeflow-examples
-
Tip When you start a terminal in Jupyter, run the command
bash
to start a bash terminal which is much more friendly then the default shell -
Tip You can change the URL from '/tree' to '/lab' to switch to using Jupyterlab
-
-
Open the notebook
mnist/mnist_aws.ipynb
-
Follow the notebook to train and deploy MNIST on Kubeflow
Follow these instructions to run the MNIST tutorial on Azure
-
Follow the Azure instructions to deploy Kubeflow on Azure
-
If you do not already have a notebook server, create a new server
-
Launch a Jupyter notebook server
- The tutorial has been tested using the Jupyter Tensorflow 1.15 image
-
Launch a terminal in Jupyter and clone the kubeflow examples repo
git clone https://github.com/kubeflow/examples.git git_kubeflow-examples
-
Tip When you start a terminal in Jupyter, run the command
bash
to start a bash terminal which is much more friendly then the default shell -
Tip You can change the URL from '/tree' to '/lab' to switch to using Jupyterlab
-
-
Open the notebook
mnist/mnist_azure.ipynb
-
Follow the notebook to train and deploy MNIST on Kubeflow
Follow these instructions to run the MNIST tutorial on IBM Cloud
-
Follow the IBM Cloud instructions to deploy Kubeflow on IBM Cloud with IBM Cloud Block Storage.
-
Launch a Jupyter notebook
- The tutorial has been tested using the Jupyter Tensorflow 1.15 and 2.1 image with persistent storage.
-
Launch a terminal in Jupyter and clone the kubeflow examples repo
git clone https://github.com/kubeflow/examples.git git_kubeflow-examples
-
Tip When you start a terminal in Jupyter, run the command
bash
to start a bash terminal which is much more friendly then the default shell -
Tip You can change the URL from '/tree' to '/lab' to switch to using Jupyterlab
-
-
Open the notebook
mnist/mnist_ibm.ipynb
-
Follow the notebook to train and deploy MNIST on Kubeflow
-
Follow these instructions to deploy Kubeflow.
-
Launch a Jupyter Notebook
- The tutorial is run on Jupyter Tensorflow 1.15 image.
- Launch a terminal in Jupyter and clone the kubeflow/examples repo
git clone https://github.com/kubeflow/examples.git git_kubeflow-examples
-
Open the notebook
mnist/mnist_vanilla_k8s.ipynb
-
Follow the notebook to train and deploy on MNIST on Kubeflow
Kaniko is used by fairing to build the model every time the notebook is run and deploy a fresh model. The newly built image is pushed into the DOCKER_REGISTRY and pulled from there by subsequent resources.
Get your docker registry user and password encoded in base64
echo -n USER:PASSWORD | base64
Create a config.json file with your Docker registry url and the previous generated base64 string
{
"auths": {
"https://index.docker.io/v1/": {
"auth": "xxxxxxxxxxxxxxx"
}
}
}
kubectl create --namespace ${NAMESPACE} configmap docker-config --from-file=<path to config.json>
Source documentation: Kaniko docs