Conventions used

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

Code in text: Indicates code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles. Here is an example: “The kms provider plugin connects kube-apiserver with an external KMS to leverage an envelope encryption principle.”

A block of code is set as follows:

apiVersion: apiserver.config.k8s.io/v1
kind: EncryptionConfiguration
resources:
  - resources:
      - secrets
    providers:
      - aesgcm:
          keys:
            - name: key-20230616
              secret: DlZbD9Vc9ADLjAxKBaWxoevlKdsMMIY68DxQZVabJM8=
      - identity: {}

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: v1
kind: ServiceAccount
metadata:
  annotations:
    eks.amazonaws.com/role-arn: "arn:aws:iam::11111:role/eks-secret-reader"
  name: service-token-reader
  namespace: default

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

$ kubectl get events
...
11m         Normal    Pulled              pod/webpage                              Container image "nginx:stable" already present on machin

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: “Another notable tool provided by GCP to improve the security posture of a GKE cluster is the GKE security posture dashboard.”

Tips or important notes

Appears like this.