Docs: runbook update

_run/kube/README.md

@@ -49,15 +49,18 @@ with it.
 Running through the entire runbook requires three terminals.
 Each command is marked __t1__-__t3__ to indicate a suggested terminal number.
 
+> **❗ Important Note:**  
+> Make sure you run all commands from the `./_run/kube` directory.
+
 If at any time you'd like to start over with a fresh chain, simply run:
 
 __t1 run__
 ```sh
-make clean kind-cluster-clean
+make clean kube-cluster-delete-kind
 make init
 ```
 
-## Initialize
+### __t1 Step: 1__ (Initialize)
 
 Start and initialize kind.
 
@@ -73,8 +76,8 @@ there may be a problem.
 
 | Option                                            | __t1 Step: 1__                                             | Explanation                                                                                                                                                        |
 |---------------------------------------------------|------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| Map random local port to port 80 of your workload | `make kind-cluster-setup`                                  | This is less error-prone, but makes it difficult to access your app through the browser.                                                                           |
-| Map localhost port 80 to workload                 | `KIND_CONFIG=kind-config-80.yaml make kind-cluster-create` | If anything else is listening on port 80 (any other web server), this method will fail.  If it does succeed, you will be able to browse your app from the browser. |
+| Map random local port to port 80 of your workload | `make kube-cluster-setup`                                  | This is less error-prone, but makes it difficult to access your app through the browser.                                                                           |
+| Map localhost port 80 to workload                 | `KIND_CONFIG=kind-config-80.yaml make kube-cluster-setup` | If anything else is listening on port 80 (any other web server), this method will fail.  If it does succeed, you will be able to browse your app from the browser. |
 
 ## Build Akash binaries and initialize network
 

_run/single/README.md

@@ -67,14 +67,17 @@ Or if it does not conflict with other local rules, use a wildcard for localhost:
 The following steps will bring up a network and allow for interacting
 with it.
 
-Running through the entire runbook requires two terminals.
-Each command is marked __t1__-__t2__ to indicate a suggested terminal number.
+Running through the entire runbook requires three terminals.
+Each command is marked __t1__-__t3__ to indicate a suggested terminal number.
+
+> **❗ Important Note:**  
+> Make sure you run all commands from the `./_run/kube` directory.
 
 If at any time you'd like to start over with a fresh chain, simply run:
 
 __t1__
 ```sh
-make clean kind-cluster-clean
+make clean kube-cluster-delete-kind
 ```
 
 ### Initialize Cluster
@@ -89,10 +92,10 @@ Pick one of the following commands:
 __t1__
 ```sh
 # Standard Networking
-make kind-cluster-setup
+make kube-cluster-setup
 
 # Calico Network Manger
-KIND_CONFIG=calico make kind-cluster-setup
+KIND_CONFIG=calico make kube-cluster-setup
 ```
 
 Check all pods in kube-system and ingress-nginx namespaces are in Running state.

_run/ssh/README.md

@@ -49,11 +49,14 @@ with it.
 Running through the entire runbook requires three terminals.
 Each command is marked __t1__-__t3__ to indicate a suggested terminal number.
 
+> **❗ Important Note:**  
+> Make sure you run all commands from the `./_run/kube` directory.
+
 If at any time you'd like to start over with a fresh chain, simply run:
 
 __t1 run__
 ```sh
-make clean kind-cluster-clean
+make clean kube-cluster-delete-kind
 make init
 ```
 
@@ -73,8 +76,8 @@ there may be a problem.
 
 | Option                                            | __t1 Step: 1__                                             | Explanation                                                                                                                                                        |
 |---------------------------------------------------|------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| Map random local port to port 80 of your workload | `make kind-cluster-setup`                                  | This is less error-prone, but makes it difficult to access your app through the browser.                                                                           |
-| Map localhost port 80 to workload                 | `KIND_CONFIG=kind-config-80.yaml make kind-cluster-create` | If anything else is listening on port 80 (any other web server), this method will fail.  If it does succeed, you will be able to browse your app from the browser. |
+| Map random local port to port 80 of your workload | `make kube-cluster-setup`                                  | This is less error-prone, but makes it difficult to access your app through the browser.                                                                           |
+| Map localhost port 80 to workload                 | `KIND_CONFIG=kind-config-80.yaml make kube-cluster-setup` | If anything else is listening on port 80 (any other web server), this method will fail.  If it does succeed, you will be able to browse your app from the browser. |
 
 ## Build Akash binaries and initialize network
 
@@ -219,13 +222,6 @@ __t1 status__
 make provider-lease-ping
 ```
 
-Get service status
-
-__t1 service status__
-```sh
-make provider-lease-status
-```
-
 Fetch logs from deployed service (all pods)
 
 __t1 service logs__