Combination of `helm update` with `--force` and PVC causes failed deployments #9

New issue

Closed

opened 2026-06-08 09:03:36 +00:00 by ryangr0 · 0 comments

ryangr0 commented

2026-06-08 09:03:36 +00:00

Owner

Originally created by @Ryangr0 on GitHub.

Originally assigned to: @Ryangr0 on GitHub.

Problem description

When github.com/webgrip/workflows@82773478e7/.github/workflows/helm-chart-deploy.yml does

helmCmd="helm upgrade --install \"$chartName\" \"$chartDir\" \
            --namespace \"$namespace\" \
            --create-namespace \
            --wait --timeout 10m --force \
            --history-max 10 \
            --atomic --cleanup-on-fail"

--force makes all values from values.yaml go into the k8s workload. Because the name is empty, it fails, and it also can't just delete pvc's.

So, we want a solution to this

Originally created by @Ryangr0 on GitHub. Originally assigned to: @Ryangr0 on GitHub. ## Problem description When https://github.com/webgrip/workflows/blob/82773478e78ff30059ce344c8de2d279ce2c0c9f/.github/workflows/helm-chart-deploy.yml does ```bash helmCmd="helm upgrade --install \"$chartName\" \"$chartDir\" \ --namespace \"$namespace\" \ --create-namespace \ --wait --timeout 10m --force \ --history-max 10 \ --atomic --cleanup-on-fail" ``` `--force` makes all values from `values.yaml` go into the k8s workload. Because the name is empty, it fails, and it also can't just delete pvc's. So, we want a solution to this

ryangr0 closed this issue

2026-06-08 09:03:37 +00:00

No labels

pull-request

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

webgrip/workflows#9

No description provided.

Rows
Columns

Combination of helm update with --force and PVC causes failed deployments #9

Problem description

Combination of `helm update` with `--force` and PVC causes failed deployments #9