...
The deployment will take about 1 hour to be fully started and stabilized, since it involves lots of components.
! Before going to the next step, please make sure all the components are running OK. !
Note: Network Slicing use case involves deploying lots of components. Depends on the system you are using, the no. of pods you have started might exceed the max-pod allowance of the system, which will cause lots of pods in status Pending. If using "kubectl describe" to show the details of the pod, you will see error message of "too many pods". Increasing the max-pod number to 200 will solve the issue. Different system set max pod in different ways. With microk8s you can open file /var/snap/microk8s/current/args/kubelet, add the line "--max-pods=200" at the end of the file, restart the service with command service snap.microk8s.daemon-kubelite restart and verify whether the date has been updated with command kubectl describe node <node_value> | grep -i capacity -A 13.
...