You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
define kubernetes_manifest resource as specified above
terraform init
terraform plan or terraform apply
Expected Behavior
No crash. Plan gets rendered or resource gets provisioned into Kubernetes.
Actual Behavior
Both terraform plan and tarraform apply crash with the panic/debug output attached above
Important 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 with Matrix Generator. Other resources (both non-argocd and argocd) get provisioned just fine.
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
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: