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

Helm – the package manager for K8s

A package manager for Kubernetes—that might sound confusing at first. We are building images with system packages and pushing those to the image registry with Docker or another tool. Why do we need a package manager?

Note

This section is not a prerequisite for passing the KCNA exam; however, it is strongly recommended reading as it might help you to avoid mistakes when using Kubernetes in real-world, practical setups.

Imagine the following scenario—you are operating a few Kubernetes clusters for a small enterprise. Those Kubernetes clusters are similar in size and configuration and run exactly the same applications, but for different environments such as development, testing, and production. The dev team was pushing for microservices architecture, and now there are about 50 microservices that run on Kubernetes working together as a part of bigger applications.

The naive way to manage the Kubernetes specifications for...