-
**Is your feature request related to a problem? Please describe.**
Deployment for kanister-operator is quite limited in options, therefore it fails under many kube-score/kube-linter tests.
Allowing …
-
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the…
-
Expand engine support to allow parameterization of an existing provider (vs always creating a new provider). This is required for some of our use cases in K8s for using parameterization to generate SD…
-
Latest Helm provider had some changes and the current configuration is no longer supported
https://github.com/rancher/terraform-rancher-server/blob/master/provider.tf#L13-L21
Here's the changelog …
-
### Is your feature request related to a problem? Please describe.
When debugging customer issues today, we have limited logging capabilities available. Broadly (ideally) we need logs from two plac…
-
### Description:
We are trying to pull the stable version of **Helm Stable** doing an `helm repo add stable https://charts.helm.sh/stable` but we are getting this error:
> Error: looks like "[h…
-
We need to explore ways to allow templating of the Helm chart values within the cluster API add-on provider fleet.
It will be beneficial when used with `Bundle` resource and defining the helm `values…
-
### Context
We're trying to remove the need of tokens to pull Helm charts from the Google Artifact Registry using Workload Identity. Our cluster runs Flux `v2.3.0` on GKE `v1.29.7`.
We've been f…
-
### Description
**Observed Behavior**:
After upgrading to v1 from 0.37.0, I've noticed that our kubelet configuration specified in the NodePools is not applied anymore.
These are some of the …
-
We have a use case where we have an existing Helm chart already released. We want to uninstall the existing Helm release but without removing any of the resources already created by the same. So we ru…