updated build test envs and build k8 docs

docs/build-k8s.md

@@ -23,7 +23,11 @@ Currently only the k8s provider kubespray is supported and included as submodule
 ### Before you Deploy
 
 Kubespray will be using OVN for all of the network functions, as such, you will need to ensure your hosts are ready to receive the deployment at a low level. While the Kubespray tooling will do a lot of prep and setup work to ensure success, you will need to prepare
-your networking infrastructure and basic storage layout before running the playbooks.
+your networking infrastructure and basic storage layout before running the playbooks. 
+
+### SSH Config
+
+The deploy has created a openstack-flex-keypair.config copy this into the config file in .ssh, if one is not there create it.
 
 #### Minimum system requirements
 
@@ -89,6 +93,8 @@ ansible-playbook host-setup.yml
 
 #### Example host setup playbook with overrides
 
+Confirm openstack-flex-inventory.yaml matches what is in /etc/genestack/inventory. If it does not match update the command to match the file names.
+
 ``` shell
 # Example overriding things on the CLI
 ansible-playbook host-setup.yml --inventory /etc/genestack/inventory/openstack-flex-inventory.yaml \
@@ -119,7 +125,8 @@ Once the inventory is updated and configuration altered (networking etc), the Ku
 ansible-playbook cluster.yml
 ```
 
-The cluster deployment playbook can also have overrides defined to augment how the playbook is executed.
+The cluster deployment playbook can also have overrides defined to augment how the playbook is executed. Confirm openstack-flex-inventory.yaml matches what is in /etc/genestack/inventory. If it does not match update the command to match the file names.
+
 
 ``` shell
 ansible-playbook --inventory /etc/genestack/inventory/openstack-flex-inventory.yaml \
@@ -133,8 +140,12 @@ ansible-playbook --inventory /etc/genestack/inventory/openstack-flex-inventory.y
 
 Once the cluster is online, you can run `kubectl` to interact with the environment.
 
+### Retrieve Kube Config
 
-### Optional - Remove taint from our Controllers
+The instructions can be found here [Kube Config](https://rackerlabs.github.io/genestack/kube-config/)
+
+
+### Remove taint from our Controllers
 
 In an environment with a limited set of control plane nodes removing the NoSchedule will allow you to converge the
 openstack controllers with the k8s controllers.
@@ -193,10 +204,14 @@ Check the node labels
 # Verify the nodes are operational and labled.
 kubectl get nodes -o wide --show-labels=true
 ```
+``` shell
+# Here is a way to make it look a little nicer: 
+kubectl get nodes -o json | jq '[.items[] | {"NAME": .metadata.name, "LABELS": .metadata.labels}]'
+```
 
 ## Install Helm
 
-While `helm` should already be installed with the **host-setup** playbook, it is possible that you may need to install helm manually on nodes. There are lots of ways to install helm, check the upstream [docs](https://helm.sh/docs/intro/install/) to learn more about installing helm.
+While `helm` should already be installed with the **host-setup** playbook, you will need to install helm manually on nodes. There are lots of ways to install helm, check the upstream [docs](https://helm.sh/docs/intro/install/) to learn more about installing helm.
 
 ### Run `make` for our helm components
 

docs/build-test-envs.md

@@ -110,3 +110,12 @@ The result of the playbook will look something like this.
 The lab deployment playbook will build an environment suitable for running Genestack, however, it does not by itself run the full deployment. Once your resources are online, you can login to the "launcher" node and begin running the deployment. To make things fairly simple, the working development directory will be sync'd to the launcher node, along with keys and your generated inventory.
 
 > If you're wanting to inspect the generated inventory, you can find it in your home directory.
+
+### SSH to lab
+
+If you have not set your .ssh config do not forget to  put in your path for your openstack-flex-keypair. Your Ip will be present after running the infra-deploy.yaml.
+
+``` shell
+ssh -i /path/to/.ssh/openstack-flex-keypair.key [email protected]
+
+```