Book Image

The KCNA Book

By : Nigel Poulton
Book Image

The KCNA Book

By: Nigel Poulton

Overview of this book

There is a huge benefit in building small, specialized, single-purpose apps that can self-heal, auto scale, and update regularly without needing downtime. Kubernetes and cloud-native technologies come in handy in building such apps. Possessing the knowledge and skills to leverage Kubernetes can positively enhance possibilities in favor of architects who specialize in cloud-native microservices applications. ‘The KCNA Book’ is designed to help those working in technology with a passion to become certified in the Kubernetes and Cloud-Native Associate Exam. You will learn about containerization, microservices, and cloud-native architecture. You will learn about Kubernetes fundamentals and container orchestration. The book also sheds light on cloud-native application delivery and observability. It focuses on the KCNA exam domains and competencies, which can be applied to the sample test included in the book. Put your knowledge to the test and enhance your skills with the all-encompassing topic coverage. Upon completion, you will begin your journey to get the best roles, projects, and organizations with this exam-oriented book.
Table of Contents (12 chapters)
9
8: Sample test
Appendix B: Sample Test answers

Kubernetes namespaces

Kubernetes namespaces are a way to divide a single Kubernetes cluster into virtual clusters called namespaces.

Each namespace can have its own set of resource quotas and user accounts. This makes them a good way to share clusters among different teams or environments. For example, you might use namespaces to divide a single cluster into dev, test, and qa namespaces. However, you shouldn’t use namespaces as a workload boundary to try and isolate hostile or potentially dangerous workloads. For example, namespaces cannot prevent a compromised container in one namespace from affecting containers in other namespaces. For example, a compromised container in the Pepsi namespace can easily take down containers in the Coke namespace. Currently, the only way to guarantee one workload won’t impact another is to put them on separate clusters.

Kubernetes namespaces quiz

1. Which of the following is a good use-case for Kubernetes namespaces?

    1. ...