5.3 KiB
Clean Kubeflow v1.2 (Minikube)
kubeflow v1.2 cannot be directly upgraded to kubeflow v1.3, you need to delete kubeflow v1.2 and install kubeflow v1.3.
Don't forget to back up your files.
Step 1：Delete minikube environment
minikube stop
minikube delete --purge
Step 2：Delete docker image
docker system prune -a
Step 3：Delete instruction packet
cd /usr/local/bin/
sudo rm -rf *
Step 4：Enable boot cleanup
cd /usr/lib/tmpfiles.d
sudo gedit tmp.conf
In line 11, uncommented indicates that startup cleanup is enabled, and comment indicates that startup cleanup is not enabled.
Ctrl + s Save after modification.
Install Kubeflow v1.3 (First minikube start)
Step 1：Open the terminal
You must make sure you can find the following files when typing ls -l on the terminal.
ls -l
Then you can proceed to the next step.
Step 2：Give execution permission
sudo chmod +x docker.sh
sudo chmod +x minikube.sh
sudo chmod +x kubeflow.sh
or
sudo chmod +x *.sh
If successful, the file name will turn green.
Then you can proceed to the next step.
Step 3：sudo ./docker.sh
sudo ./docker.sh
reboot VM or computer.
Then confirm the docker version.
If you can see Clinet and Server versions, it means success.
Step 4：sudo ./minikube.sh
sudo ./minikube.sh
After success, you will see the following screen. (first time)
Next, you can change the owner of the .kube and .minikube folders.
In this way, subsequent commands related to kubectl and minikube do not need to add sudo.
The line with the second red exclamation mark indicates the storage location of .kube and .minikube.
sudo chown -R <user_name> .kube .minikube
You can enter ls -l -a to confirm, the first name is the owner and the second name is the group.
ls -l -a
It’s okay if you don’t do this step to change the owner, you can skip it directly.
Step 5：sudo ./kubeflow.v13.sh
sudo ./kubeflow.v13.sh
After execution, enter the following command to observe the pods status:
kubectl get pods -n kubeflow
It takes about 30 minutes to wait for 16G RAM.
After seeing the same situation as on the screen, you can proceed to the next step.
Step 6：Port-forward
After all the pods are running
kubectl port-forward -n istio-system svc/istio-ingressgateway 8080:80
Input in the browser
http://localhost:8080/
or
127.0.0.1:8080
- Email Address：user@example.com
- Password：12341234
Step 7：Disable boot cleanup
cd /usr/lib/tmpfiles.d
sudo gedit tmp.conf
In line 11, uncommented indicates that startup cleanup is enabled, and comment indicates that startup cleanup is not enabled.
Ctrl + s Save after modification.
Kubeflow installed on Minikube will store data in /tmp/hostpath-provisioner.
The data in /tmp will be deleted after shutdown.
To ensure that the data is not deleted, this function needs to be disabled.
Second minikube start
After the installation is complete and startup cleanup is disabled, you can shut down your computer without worrying about data loss. After restarting the computer or virtual machine, enter:
minikube stop
Close Minikube completely, and enter:
minikube start
Wait for Minikube to start.
After starting, confirm whether the Pod is running. After running, you can execute port-forward.