Book Image

kubectl: Command-Line Kubernetes in a Nutshell

By : Rimantas Mocevicius
Book Image

kubectl: Command-Line Kubernetes in a Nutshell

By: Rimantas Mocevicius

Overview of this book

The kubectl command line tool lets you control Kubernetes clusters to manage nodes in the cluster and perform all types of Kubernetes operations. This introductory guide will get you up to speed with kubectl in no time. The book is divided into four parts, touching base on the installation and providing a general overview of kubectl in the first part. The second part introduces you to managing Kubernetes clusters and working with nodes. In the third part, you’ll be taken through the different ways in which you can manage Kubernetes applications, covering how to create, update, delete, view, and debug applications. The last part of the book focuses on various Kubernetes plugins and commands. You’ll get to grips with using Kustomize and discover Helm, a Kubernetes package manager. In addition to this, you’ll explore how you can use equivalent Docker commands in kubectl. By the end of this book, you’ll have learned how to install and update an application on Kubernetes, view its logs, and inspect clusters effectively.
Table of Contents (16 chapters)
Section 1: Getting Started with kubectl
Section 2: Kubernetes Cluster and Node Management
Section 3: Application Management
Section 4: Extending kubectl

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.