After a virtual machine is provisioned and booted, we can echo the server and check that the cluster is deployed properly. Here, we’ll use a yaml file called kube_cluster_config604.yml (but your name may be different). That file should be in the directory with the cloned repo. We’ll kick it off with the kubectl binary. First, we’ll run a simple kubectl defining the –kubeconfig and then the yml file and apply a command that is an echo.yml (to see an example of that, check out( https://github.com/spinnaker/echo/blob/master/echo-web/config/echo.yml):
kubectl --kubeconfig kube_cluster_config604.yml apply -f echo.yml
We can then check the deployment using a get verb followed by pod, deployment, ingress, and sac:
kubectl --kubeconfig kube_cluster_config604.yml get pod
kubectl --kubeconfig kube_cluster_config604.yml get deployment
kubectl --kubeconfig kube_cluster_config604.yml get svc
kubectl --kubeconfig kube_cluster_config604.yml get ingress
In this case, the 604 postfix was created by a script that renames the yaml files when they’re checked in following a commit. The echo might also be version controlled (e.g. if we decide to use a different port or change one of the settings).