Open ivankorn opened 2 months ago
If anyone is interested in temporary workaround for this issue:
# Workaround for https://github.com/hashicorp/terraform-provider-kubernetes/issues/2580
module "kubectl-argocd-application-set" {
source = "terraform-google-modules/gcloud/google//modules/kubectl-wrapper"
version = "~> 3.4"
project_id = local.gcp_project_id
cluster_name = module.gke.name
cluster_location = module.gke.location
module_depends_on = [module.gke.endpoint]
kubectl_create_command = "kubectl create -f argocd/application-set.yaml"
kubectl_destroy_command = "kubectl delete -f argocd/application-set.yaml"
skip_download = true
}
Terraform Version, Provider Version and Kubernetes Version
Affected Resource(s)
Terraform Configuration Files
ApplicationSet Manifest (works with
kubectl create -f
)Debug Output
debug.log
Panic Output
crash.log
Steps to Reproduce
ApplicationSet
manifest as specified abovekubernetes_manifest
resource as specified aboveterraform init
terraform plan
orterraform apply
Expected Behavior
No crash. Plan gets rendered or resource gets provisioned into Kubernetes.
Actual Behavior
Both
terraform plan
andtarraform apply
crash with the panic/debug output attached aboveImportant Factoids
Non-matrix, f.e.
Cluster Generator
works fine. To the best of my knowledge the problem is reproducible only with ArgoCD's Application Set withMatrix Generator
. Other resources (both non-argocd and argocd) get provisioned just fine.References
Note: My issue is slightly different because I'm using the new
provider::kubernetes::manifest_decode
provider function to define manifest. But I get very similar (or the same) error.Community Note