Helm Commands Cheatsheet

-

Hi everyone😎, Sharing helm commands that I use day to day.

helm create:
This command creates a chart directory along with the common files and directories used in a chart.
  1. Create a new chart with the given name:- helm create [CHART]

helm install: 
This command installs a chart in a cluster.
  1. Install particular service using helm:- 
    • helm install [RELEASE_NAME] [CHART]
  2. Install chart in particular namespace:-
    • helm install [RELEASE_NAME] [CHART] --namespace [NAMESPACE]
  3. Override the default values with those specified in a file of your choice:-
    • helm install [RELEASE_NAME] [CHART] --namespace [NAMESPACE] --values [yaml-file/url]
  4. Dry run helm chart:-  helm install [RELEASE_NAME] [CHART] --dry-run
  5. Install in verbose mode:- helm install [RELEASE_NAME] [CHART] --debug
  6. Set values on the command:- helm install [RELEASE_NAME] [CHART] --set [KEY]=[VALUE]
helm lint:
This command takes a path to a chart and runs a series of tests to verify that the chart is well-formed.
  1. Examine a chart for possible issues:- helm lint [CHART]
helm list:
This command lists all of the releases for a specified namespace
  1. List releases:- helm list [FLAG]  or helm ls [FLAG] 

helm uninstall:
This command takes a release name and uninstalls the release.
  1. Uninstall deployed release:- helm uninstall [RELEASE_NAME]
  2. Uninstall deployed release in specific namespace:- helm uninstall [RELEASE_NAME] --namespace [NAMESPACE]

helm upgrade:
This command upgrades a release to a new version of a chart.
  1. Upgrade a release:- helm upgrade [RELEASE_NAME] [CHART]
  2. Upgrade a release by overriding the values with those specified in the file:- helm upgrade [RELEASE_NAME] [CHART]
  3. Upgrade a release. If it does not exist on the system, install it:- helm upgrade [RELEASE_NAME] [CHART] --install
  4. Upgrade to a specified version:- helm upgrade [RELEASE_NAME] [CHART] --version [VERSION-NUMBER]

helm repo:
This command is used to add, remove, list, and index chart repositories.
  1. Add a chart repository:- helm repo add [URL]
  2. Update information of available charts locally from chart repositories:- helm repo update
  3. List chart repositories:- helm repo list

helm rollback:
This command rolls back a release to a previous revision.
  1. Roll back a release to a previous revision:- helm rollback [RELEASE_NAME] [REVISION]

helm search:
Search provides the ability to search for Helm charts in the various places they can be stored including the Artifact Hub and repositories we have added.
  1. Search for charts in the Artifact Hub or your own hub instance:- helm search hub [KEYWORD] [flags]
  2. Search repositories for a keyword in charts:- helm search repo [KEYWORD] 
Hope you like my blog post

Comments

Post a Comment

Please give us your valuable feedback

Popular posts from this blog

MySQL Multi Source Master Slave Replication using GTID

-
Image
We are using GTID-based master-slave replication. In this replication, both master and slave should have the same GTID. This blog post aims to provide a step-by-step guide to help you set up MySQL Replication using GTIDs and help you replicate your MySQL data with ease. Prerequisite Master Source 1 Channel name:  DEVELOPMENT Database: mydb1 Enable Replication For Tables testing1 testing2 testing3 Mysql Server Running: 192.168.0.201:3307 Master Source 2 Channel name:  PRODUCTION Database: mydb1 Enable Replication For Tables testing4 testing5 testing6 Mysql Server Running: 192.168.0.201:3308 Slave Mysql Server Running: 192.168.0.209:3306 Configuration of  masters(192.168.0.201:3307/192.168.0.201:3308) and slave (192.168.0.209:3306) my.cnf config for master (192.168.0.201:3307) my.cnf config for master (192.168.0.201:3308) my.cnf config for slave (192.168.0.209:3306) Steps for taking a dump and restoring it Run the following commands in both masters 192.168.0.201:3307 and 1...
Read more

Access and modify all the resources of our Wiki.js using WikiJS API

-
Image
Hi everyone 😎 , Today we are going to see how to access or modify WikiJS resources using WikiJS API. WikiJS exposes GraphQL API to access and modify the stuff according to our requirements. So In this blog post, we going to see  How to set up WikiJS's local environment using docker. How to generate an API token in Wikijs. Using API tokens how to access WikiJS resources and how to modify them. First Local Setup using docker Here I am using docker to set up my local isolated WikiJS environment. Below is my docker-compose.yml file written by WikiJS contributors. To build the WikiJS environment we just need to run the following command  docker-compose up -df  [PATH_OF_DOCKER_COMPOSE_YML_FILE] To check the environment is in a running state run the following command docker ps Second Generate API token After setup our local environment we are ready to create our initial Administrator account in our WikiJS. 1. On the browser type localhost:80 2. Create an Administrator acco...
Read more

How to pass parameters in webhook?

-
Image
Hey everyone 😊, Today I want to share another interesting thing which I found in StackOverflow and that is how to pass parameters in webhook. Those who don't know about webhook I advise you to google about it before going further reading.  So for demonstration purpose, I am going to use Jenkins and Generic Webhook plugin . I created a job and called it testing  and select Generic Webhook  Trigger . Thereafter I add Request Parameter   and in the request parameter I added the name of the request which is name Thereafter I added a token to specify that this job can only be triggered. After this, I select Execute Shell from Build  and write the following code  After doing this add webhook URL in bitbucket repository or  GitHub repository with the parameter. The URL is look something like this  Webhook URL:- https://[YOUR_JENKINS_URL]/generic-webhook-trigger/invoke?token=trigger&name=Svastikkka  The configuration will something like this ...
Read more