Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
kubectl: Command-Line Kubernetes in a Nutshell

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

Arrow left icon
Product type Paperback
Published in Nov 2020
Publisher Packt
ISBN-13 9781800561878
Length 136 pages
Edition 1st Edition
Concepts
Arrow right icon
Author (1):
Arrow left icon
Rimantas Mocevicius Rimantas Mocevicius
Author Profile Icon Rimantas Mocevicius
Rimantas Mocevicius
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

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

Removing nodes

The gke-kubectl-lab-default-pool-b3c7050d-8jhj node got drained and is not running any deployments, pods, or StatefulSets, so it can be easily deleted now.

We do it using the delete node command:

$ kubectl delete node gke-kubectl-lab-default-pool-b3c7050d-8jhj

We delete the node using the preceding command. The output of this command is as shown in the following screenshot:

Figure 3.12 – Delete node

As you can see from the kubectl get nodes output, the node was unregistered from the Kubernetes API and got deleted.

Important note

Actual node deletion depends on your Kubernetes setup. In cloud-hosted clusters, the node gets unregistered and deleted, but if you are running an on-premise self-hosted Kubernetes cluster, the actual node will not be deleted but only deregistered from the Kubernetes API.

Also, when you specify the cluster size in the cloud setup, the new node will replace the deleted one after some time.

...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime