Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
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

Rolling back to a previous Helm release

In this section, let's see how to roll back to a previous version using the helm rollback command.

The helm rollback command is unique to Helm, and it allows us to roll back the whole application, so you do not have to worry about which Kubernetes resources need to be rolled back specifically.

Of course, when dealing with the release IDs of real-world applications, database schemas get changed as well, so to roll back the frontend application, you have to roll back the database schema changes too. This means that things aren't always so straightforward as they may seem here, but using Helm still simplifies some parts of the application release rollback process.

To run the helm rollback command, we first need to know the release revision we want to roll back to, which we can find with the following command:

$ helm history postgresql

The output of the preceding command is shown in the following screenshot:

...
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 $19.99/month. Cancel anytime
Banner background image