duplicate entry for /v1, Kind=APIResourceList error in v3.1.0 when running terraform plan for an existing helm_release with CRDs #1717
Description
Terraform, Provider, Kubernetes and Helm Versions
Terraform v1.13.4
Provider: hashicorp/helm v3.1.0
Kubernetes Version:1.33.5
Helm Version: "v3.19.
Affected Resource(s)
helm_release
Terraform Configuration Files
resource "helm_release" "cert_manager" {
name = "cert-manager"
repository = "https://charts.jetstack.io"
chart = "cert-manager"
version = "v1.19.1"
namespace = "cert-manager"
skip_crds = false
atomic = true
cleanup_on_fail = true
max_history = 10
values = [
<<EOF
crds:
enabled: true
serviceAccount:
annotations:
iam.gke.io/gcp-service-account: "[email protected]"
featureGates: "ServerSideApply=true"
EOF
]
}Debug Output
Panic Output
Steps to Reproduce
terraform plan
Expected Behavior
Should be able to update an existing Helm release
Actual Behavior
Error: Parser Error
with helm_release.cert_manager,
on cert_manager.tf line 1, in resource "helm_release" "cert_manager":
1: resource "helm_release" "cert_manager" {
duplicate entry for /v1, Kind=APIResourceList
Error: Error setting release attributes
with helm_release.cert_manager,
on cert_manager.tf line 1, in resource "helm_release" "cert_manager":
1: resource "helm_release" "cert_manager" {
Unable to set attributes for helm release cert-manager
Important Factoids
K8s cluster runs in GKE.
When running the same code with provider version 3.0.2 it works just fine. In fact, I have the same issue with nginx-ingress, where I also install CRDs. Resources without CRD installations are not affected.
References
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment