You're reading from kubectl: Command-Line Kubernetes in a Nutshell Deploy, manage, and debug container workloads using the Kubernetes CLI

Product type Paperback

Published in Nov 2020

Publisher Packt

ISBN-13 9781800561878

Length 136 pages

Edition 1st Edition

Tools

Kubernetes

Concepts

DevOps

Author (1):

Rimantas Mocevicius

View More author details

Table of Contents (16) Chapters

Preface

1. Section 1: Getting Started with kubectl

2. Chapter 1: Introducing and Installing kubectl FREE CHAPTER

3. Section 2: Kubernetes Cluster and Node Management

4. Chapter 2: Getting Information about a Cluster

5. Chapter 3: Working with Nodes

6. Section 3: Application Management

7. Chapter 4: Creating and Deploying Applications

8. Chapter 5: Updating and Deleting Applications

9. Chapter 6: Debugging an Application

10. Section 4: Extending kubectl

11. Chapter 7: Working with kubectl Plugins

12. Chapter 8: Introducing Kustomize for Kubernetes

13. Chapter 9: Introducing Helm for Kubernetes

14. Chapter 10: kubectl Best Practices and Docker Commands

15. Other Books You May Enjoy

Leave a review - let other readers know what you think

Scheduling application replicas to different nodes (pod affinity)

Using nodeAffinity does not ensure that pods will next time be scheduled onto separate nodes, and for real application high availability, the best practice is to ensure that application pods are scheduled onto separate nodes. If one of the nodes is down/rebooted/replaced, having all the pods running on that node will cause the application to go down and its services to be unavailable.

Let's update the deployment.yaml file with the podAntiAffinity rule so that the nginx application is only scheduled to gke-kubectl-lab-we-app-pool and onto separate nodes:

...
spec:
  affinity:
    nodeAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
        nodeSelectorTerms:
        - matchExpressions:
          - key: node...