To get the most out of this book
You should have some basic Linux experience, understand concepts of containers, and be familiar with networking basics.
Be attentive and read the special “Interview tips” sections.
Download the example code files
The code bundle for the book is hosted on GitHub at https://github.com/PacktPublishing/Cracking-the-Kubernetes-Interview. We also have other code bundles from our rich catalog of books and videos available at https://github.com/PacktPublishing. Check them out!
Conventions used
There are a number of text conventions used throughout this book.
CodeInText: Indicates code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and X/Twitter handles. For example: “The restartPolicy parameter is set to Never, so if the container exits, the Job will not restart it unless the Pod fails.”
A block of code is set as follows:
---
apiVersion: v1
kind: Service
metadata:
name: hello-sample-ext
namespace: default
spec:
type: ExternalName
externalName: google.com
Any command-line input or output is written as follows:
Kubectl get pods
Bold: Indicates a new term, an important word, or words that you see on the screen. For instance, words in menus or dialog boxes appear in the text like this. For example: “Automatic recovery process, often called a reconciliation loop, is a cornerstone of Kubernetes’ resilience.”
Warnings or important notes appear like this.
Tips and tricks appear like this.
