More instructions for Task #10

Signed-off-by: Marco Emilio "sphakka" Poleggi <marcoep@ieee.org>

README.md

@@ -709,3 +709,17 @@ Once done, use the following test track to finalize your workflow:
      - `metallb-native.yaml` triggers a whole app stack redeployment. :bulb:
        `kubectl apply` can be called on a running stack.
      - `metallb.yaml` triggers only the load balancer service redeployment.
+
+:star: Bonus features/tasks:
+  * Task grouping by blocks.
+  * `rebuild all` no-op task to force rebuilding the KinD cluster and
+    redeploying the load-balancer service via a signal.
+  * `check KinD` task that verifies the existence of a running cluster and,
+    when changed, notifies the cluster creation.
+  * `delete cluster` task to force deleting the KinD cluster.
+  * `expose LB IP` handler for launching `socat` (must be installed!) so that
+    you can connect to the cluster from your workstation (see [Tips & Tricks
+    for
+    K8s](https://gitedu.hesge.ch/lsds/teaching/bachelor/cloud-and-deployment/lab-k8s#tips-and-tricks)).
+  * `re-expose LB IP` no-op tasks to trigger manually the `expose LB IP`
+    handler.