First Kubernetes Application
This scenario takes you through the basics of deploying an application on Kubernetes. The application is nothing notable, but it's simple enough to get started. In the following steps you will learn:
- to deploy and start the echoserver application
- to scale the application
- Services load balance between multiple Pods of the app
- Kubernetes resilience maintains the declared state even with failures
- to rollout a new version of an application
It's not vital, but you may want to first walk through the introduction to Kubernetes covered in the Minikube scenario of this course.
Once an application is in a container, it's fairly simple to ask Kubernetes to serve up the container in multiple Pods fronted with a load balancing Service. Thereafter, Kubernetes dutifully respects your declared request by ensuring the application remains running on the cluster.
There are many other types of resources that can be added to Kubernetes besides just Pods, Services and Deployments, however these are the most common resources. Later, explore the Helm scenarios to see how whole charts of more complex deployments can be installed.
With these steps you have learned:
- ✔ how to Deploy an application,
- ✔ how to Scale an application,
- ✔ how to load balance an application with a Service for multiple Pods of an application,
- ✔ how Resilience maintains the declared state even with failures,
- ✔ how to Roll out new versions of an application.
Your Kubernetes Cluster
For this scenario, Katacoda has just started a fresh Kubernetes cluster for you. Verify it's ready for your use.
kubectl version --short && \
kubectl get componentstatus && \
kubectl get nodes && \
The Helm package manager used for installing applications on Kubernetes is also available.
helm version --short
You can administer your cluster with the
kubectl CLI tool or use the visual Kubernetes Dashboard. Use this script to access the protected Dashboard.