Conventions used

There are a number of text conventions used throughout this book.

Code in text: Indicates code words in text, resource name, folder names, filenames, file extensions, pathnames, dummy URLs, or user input.

Here is an example: “As described in the Kubernetes components section, we interact with clusters using a YAML file called kubeconfig in the $HOME/.kube/config directory.”

A block of code is set as follows:

apiVersion: apps/v1
kind: ReplicaSet
metadata:
  name: frontend
  labels:
    app: guestbook
    tier: frontend
spec:
  replicas: 3
  selector:
    matchLabels:
      tier: frontend
  template:
    metadata:
      labels:
        tier: frontend
    spec:
      containers:
      - name: php-redis
        image: gcr.io/google_samples/gb-frontend:v3

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

apiVersion: apps/v1
kind: ReplicaSet
metadata:
  name: frontend
  labels:
    app: guestbook
    tier: frontend

Any command-line input or output is written as follows:

gcloud components install kubectl
sudo apt-get install kubectl

Bold: Indicates a new term, an important word, or words that you see onscreen. For instance, words in menus or dialog boxes appear in bold. Here is an example: “ You can check your Google Cloud expenditure and remaining days in Billing Account Overview.”

Tips or important notes

Appear like this.