Updated deployment steps

doc/deployment_guide.md

@@ -704,8 +704,14 @@ sudo systemctl restart docker
 # Install MicroK8s
 sudo snap install microk8s --classic --channel=1.29/stable
 
+# Wait until MicroK8s is ready
+microk8s.status --wait-ready
+
 # Create alias for command "microk8s.kubectl" to be usable as "kubectl"
 sudo snap alias microk8s.kubectl kubectl
+
+# Create alias for command "microk8s.helm3" to be usable as "helm3"
+sudo snap alias microk8s.helm3 helm3
 ```
 
 It is important to make sure that `ufw` will not interfere with the internal pod-to-pod
@@ -796,14 +802,12 @@ If so, execute it and retry enabling `community` addon.
 The __mandatory__ addons to be enabled are:
 
 - `dns`: enables resolving the pods and services by name
-- `helm3`: required to install NATS
 - `hostpath-storage`: enables providing storage for the pods (required by `registry`)
 - `ingress`: deploys an ingress controller to expose the microservices outside Kubernetes
 - `registry`: deploys a private registry for the TFS controller images
 
 ```bash
 microk8s.enable dns
-microk8s.enable helm3
 microk8s.enable hostpath-storage
 microk8s.enable ingress
 microk8s.enable registry
@@ -832,12 +836,6 @@ To confirm everything is up and running:
    until all pods are __Ready__ and __Running__.
 3. If it takes too long for the Pods to be ready, __we observed that rebooting the machine may help__.
 
-Then, create aliases to make the commands easier to access:
-
-```bash
-sudo snap alias microk8s.helm3 helm3
-```
-
 If `linkerd` is enabled, run the following commands to add the alias to the command, and validate it is working correctly:
 
 ```bash