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

CI/CD and GitOps

You might have heard it before, CI stands for Continuous Integration and CD for Continuous Delivery or sometimes Continuous Deployment.

Continuous Integration

Is a practice and process automation targeting developers. With CI, code changes are regularly built, tested and integrated into a shared repository (branch/trunk/etc.)

CI is viewed as a solution to the problem of having too many changes in development at once that might conflict with each other and being hard to merge. The ultimate goal is to ensure that the software is always in the working state and in case automated tests fail, the team has to fix the problem first, before continuing with development.

Continuous Delivery

Usually refers to an automation in the pipeline where the tested code changes mark a release that is uploaded to a package repository or container image. From there on, the image or a package can be deployed after approval.

Continuous Delivery can be seen as a way to align...