-
# Problem
The automated "new version" Helm Chart releases are failing.
Reference: https://github.com/RequestNetwork/request-helm-charts/actions/workflows/new-version.yaml
Example: https://github.com/…
-
## Hello!
- Vote on this issue by adding a 👍 reaction
- If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)
## Issue details
When …
-
**Describe the rationale for the suggested feature.**
Now that we collect [helm release information](https://troubleshoot.sh/docs/collect/helm/), the natural step forward is using this information …
-
### Describe the bug
Here is the config file that I have for creating the `rook-ceph-cluster` as defined [here](https://artifacthub.io/packages/helm/rook/rook-ceph-cluster). I can deploy using almo…
-
## Release Checklist
- [ ] Network-operator related component versions in Helm chart are up to date. (otherwise, submit PR to update)
- [ ] node-feature-discovery
- [ ] SR-IOV Network Operato…
-
Helm should be used to create helm-releases. That is the way how helm is supposed to be used. The documentation of helm refers to the scenario where helm is used that way. `helm template` is useful fo…
-
-
### Which tests are failing?
https://github.com/spidernet-io/spiderpool/actions/runs/10514834350/job/29133837113
helm/kind-action@v1.10.0 , use (default: v0.21.0)
https://github.com/helm/kind-…
-
It would be nice to have documentation here on how to manage HELM releases when the chart version has not changed, but rather when the **_values_** under the spec have changed in the connected git rep…
-
Opening in new tab on releases with count less than three will result in 404, in any browser.