#Mini-problem with the Helm chart

1 messages · Page 1 of 1 (latest)

fading ferry
#

Not sure if this is an expectancy on k8s that is false on my part or an issue with the Helm chart. I have Dagger installed as a daemon set with only one container and when I upgrade, the container stays "in progress" and never leaves that state. I can fix it by rerunning the installation.

Again, a mini-problem. Any help though to fix either my expectations or the Helm chart would be appreciated.

carmine nymph
fading ferry
#

Commenting, so the thread doesn't disappear on us. 🙂

carmine nymph
#

checking this now @fading ferry 😄

#

sorry, had a super busy

#

@fading ferry when you're saying "when I upgrade" are you referring to helm upgrade --install?

carmine nymph
#

@fading ferry I wasn't able to repro at a first glance. I performed a pretty trivial helm upgrade in a new k8s cluster and haven't observed any pending states.

  1. First I ran this to deploy a specific helm chart version: helm upgrade --install --namespace=dagger --create-namespace dagger oci://registry.dagger.io/dagger-helm --version 0.15.0

I verified all is good with helm -n dagger list and kubectl -n dagger get pods

  1. I perform the upgrade with helm upgrade --install --namespace=dagger --create-namespace dagger oci://registry.dagger.io/dagger-helm afterwards and I can verify that both helm -n dagger list and kubectl -n dagger get podsshow everything's good
fading ferry
#

Hmm.. what version of k8s were you using? I'm on k3s v1.27. 16. It might be an issue with k3s. 🤔

carmine nymph