Book Image

Becoming KCNA Certified

By : Dmitry Galkin
Book Image

Becoming KCNA Certified

By: Dmitry Galkin

Overview of this book

The job market related to the cloud and cloud-native technologies is both growing and becoming increasingly competitive, making certifications like KCNA a great way to stand out from the crowd and learn about the latest advancements in cloud technologies. Becoming KCNA Certified doesn't just give you the practical skills needed to deploy and connect applications in Kubernetes, but it also prepares you to pass the Kubernetes and Cloud Native Associate (KCNA) exam on your first attempt. The book starts by introducing you to cloud-native computing, containers, and Kubernetes through practical examples, allowing you to test the theory out for yourself. You'll learn how to configure and provide storage for your Kubernetes-managed applications and explore the principles of modern cloud-native architecture and application delivery, giving you a well-rounded view of the subject. Once you've been through the theoretical and practical aspects of the book, you'll get the chance to test what you’ve learnt with two mock exams, with explanations of the answers, so you'll be well-prepared to appear for the KCNA exam. By the end of this Kubernetes book, you'll have everything you need to pass the KCNA exam and forge a career in Kubernetes and cloud-native computing.
Table of Contents (22 chapters)
1
Part 1: The Cloud Era
4
Part 2: Performing Container Orchestration
7
Part 3: Learning Kubernetes Fundamentals
12
Part 4: Exploring Cloud Native
16
Part 5: KCNA Exam and Next Steps

Summary

In this chapter, we’ve learned a lot about container runtimes, container interfaces, and service meshes. A container runtime is low-level software that manages basic container operations such as image downloading and the start or deletion of containers. Kubernetes does not have its own runtime, but it provides interfaces that allow you to use different runtimes, different network plugins, different storage solutions, and different service meshes. Those interfaces are called CRI, CNI, CSI, and SMI respectively and their introduction allowed a lot of flexibility when using K8s.

We’ve also learned about container runtime types and their differences. Namespaced containers are the most popular and lightweight, however, they are not as secure as other types. Virtualized containers are the slowest, but they provide maximum security as each container uses an individual Linux kernel. Sandboxed containers fill the gap between the other two – they are more secure...