25% off on first invoice for all services*

SPRING SALE

Use coupon

*Offer valid for new customers only

25% off on first invoice for all services*

SPRING SALE

Use coupon

*Offer valid for new customers only

Need help?

Our experts have had an average response time of 11.43 minutes in March 2024 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

Delete Helm Deployment and Namespace easily

by | Oct 23, 2021

In case of unwanted or multiple copies, we can delete Helm Deployment and Namespace to free up space.

As part of our Server Management Services, we assist our customers with several Kubernetes queries.

In order to begin, our Support Techs recommend to install and configure a Kubernetes cluster, Helm, and access to a CLI or terminal.

 

  • Delete Helm Deployment

When we delete a Helm deployment it removes the components without deleting the namespace.

Now, let us see the steps our Support Techs employ to do the same.

1. Initially, we need to list Helm Deployments in the current namespace.

To do so, we run:

helm list

Then to list deployments in a specific namespace, we run:

helm list --namespace

And to list all Helm deployments in all namespaces, we run:

helm list --all-namespaces

This example shows deployments of the same name existing on different namespaces.

We need to find the exact release and the namespace.

2. Delete Helm Deployment

We may have already installed a Helm deployment. To remove that, we run:

helm uninstall  --namespace

Alternatively, we use the alias:

helm delete  --namespace

As a result, we can see a confirmation of removal.

For example, the command below removes a deployment named bob-chart on the namespace other:

helm uninstall bob-chart --namespace other

In Helm 2, we use the –purge option to delete the release and related Kubernetes components:

helm delete  --purge

Finally, we list Helm deployments to confirm the release is no longer there.

  • Delete Helm Deployment and Namespace

When we delete the namespace, it deletes all the residing components. However, when we remove all deployments within a namespace, it does not remove the namespace.

Although we can generate a namespace when deploying a chart with –create-namespace, there is no method to remove it when we delete a release using Helm commands.

We can delete the namespace using the kubectl command.

1. To do so, we list all Namespaces

kubectl get namespace

The output will print all the namespaces, their status, and age.

2. Then we delete the Namespace

kubectl delete 

Now, the terminal will print a confirmation message.

For example, suppose we want to remove the other namespace. For that, we run:

kubectl delete namespace other

The namespace will no longer appear on the list and is available to use again.

[Stuck in between? We are here to assist you]

 

Conclusion

In short, we need to give careful consideration when we remove a Helm deployment or namespace. Today, we saw how our Support Techs perform the same.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF