search

headlamp-k8s / headlamp

A Kubernetes web UI that is fully-featured, user-friendly and extensible
https://headlamp.dev
Apache License 2.0
2.36k stars 170 forks source link

Helm Rollback deploys to wrong namespace #2442

Open Xzelsius opened 1 month ago

Xzelsius commented 1 month ago

We have several different namespaces, all with their different Helm releases.

One of our releases in the namespace grcsaas-default had an issue, and we had to roll back to a previous version. We did this using Headlamp.

image

But instead of reverting the deployment in namespace grcsaas-default it deployed the previous release to the default namespace.

image

Normally, our default namespace is empty as we don't deploy anything there

image

Is this intentional, if so, is there a way (in the UI, we know how to do it in the CLI) to roll back the release in its current namespace instead?

skoeva commented 4 weeks ago

Hi! The issue you are seeing is not intentional, currently looking into this. In the meantime, just to confirm, is this only occurring when rolling back in the UI? And are there any additional details in your setup that might be helpful for recreating the issue?

Xzelsius commented 4 weeks ago

I only tested it in one of our Azure Kubernetes Clusters. If I find some time tomorrow I can try it out in another cluster or with another Helm Chart to see if it happens for everything.

Using the Helm CLI does work without issue

skoeva commented 2 weeks ago

@Xzelsius Just a reminder: if you are still running into this issue and would like us to get a fix in, any additional info would be super useful here as I've personally been unable to reproduce this locally

Xzelsius commented 2 weeks ago

So I tested it again with the v1.30.5 with the Redis Helm Chart

  1. I created a completely new AKS cluster
  2. Then I deployed Redis using 
    helm install redis --namespace redis --create-namespace oci://registry-1.docker.io/bitnamicharts/redis
  3. Few seconds later, I was able to confirm that everything was running correctly in the namespace redis
  4. Then I upgraded Redis using 
    helm upgrade redis --namespace redis --create-namespace oci://registry-1.docker.io/bitnamicharts/redis
  5. Few seconds later, I was able to confirm that everything still was running correctly in the namespace redis
  6. Then I opened Headlamp and went to Apps > Installed and selected the Redis App image
  7. Then I clicked on the rollback button and selected rev. 1 and clicked on Revert
  8. Few seconds later, I was able to confirm that everything still was running correctly in the namespace redis

So using a very basic Helm Chart works without any issue!

But at our company, we use an umbrella chart which contains 3 or 4 child Helm Charts. I have yet to try this out on the new AKS cluster (not so easy because the Chart is not public available, and neither are the images)