What's Next?

Summary

We have a production-ready Kubernetes cluster running in AWS. Isn’t that something worth a celebration?

kOps has proven to be relatively easy to use. We executed more aws than kops commands. If we exclude them, the whole cluster can be created with a single kOps command. We can easily add or remove worker nodes. Upgrades are simple and reliable, if a bit long. The important part is that we can avoid downtime through rolling upgrades.

There are a few kops commands we did not explore. You can learn more about the additional commands through the documentation.

You might think that you are ready to apply everything you learned so far. We are not done yet. There’s still one significant topic we need to explore.

We postponed the discussion about stateful services since we did not have the ability to use external drives. We did use volumes, but they were all local and do not qualify as persistent. Failure of a single server would prove that. Now that we are running a cluster in AWS, we can explore how to deploy stateful applications.

---

In the next lesson, we’ll go through a comparison of Kubernetes Operations (kOps) with D4AWS.