Merge branch 'master' of github.com:valayDave/metaflow-on-kubernetes-docs

Author: valayDave

Readme.md

@@ -124,6 +124,6 @@ This involves using AWS Creds to set environment variables that give access to a
         "METAFLOW_DEFAULT_METADATA": "service"
     }
     ```
-- The plugin supports deploying a Metaflow-runtime into kubernetes. use the `kube-deploy run` command with any Flow to deploy directly to Kubernetes. Check usage example [here](https://github.com/valayDave/metaflow-kube-demo). The ``metaflow-native-cluster-role.yml`` enables the Metaflow plugin to work within Kubernetes to orchestrate jobs using the using its native runtime. It is basically allowing `default` kubernetes namespace to have an admin role in deployment.(Security not top notch for purpose of demo)  
+- The plugin supports deploying a Metaflow-runtime into kubernetes using the `kube-deploy run` command. Check usage example [here](https://github.com/valayDave/metaflow-kube-demo). The ``metaflow-native-cluster-role.yml`` enables the Metaflow plugin to work within Kubernetes to orchestrate jobs using the using its native runtime within a container in the cluster. It is basically allowing `default` kubernetes namespace to have an admin role in applied to pods within the namespace.(I know not the best. But its a demo. Will Figure better security.)  
 - Once Done Executing : 
     - Once the ``kubectl port-forward deployment/metaflow-metadata-service 8080:8080`` to port forward metatdata service for accesss on localmachine. Please note that because this is directly port forwarding to the pod were are taking the 8080 port for the service.