-
Notifications
You must be signed in to change notification settings - Fork 1k
Open
Labels
Description
Terraform Version, Provider Version and Kubernetes Version
Terraform version: 1.5.7
Kubernetes provider version: 2.35.0
Kubernetes version: Microk8s 1.32.9
Affected Resource(s)
Terraform Configuration Files
# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.Debug Output
Panic Output
https://gist.github.com/alyssaruth/e7effa1f87b225c95a9a073fb2874820
Steps to Reproduce
Happened during a terraform apply, we've only seen it occur once so likely some rare race condition
Expected Behavior
No crash
Actual Behavior
Terraform bombs out with a bunch of errors like:
09:52:35 │ Error: Plugin did not respond
09:52:35 │
09:52:35 │ with module.test_control["k8s110-ms2"].kubernetes_persistent_volume_claim_v1.main,
09:52:35 │ on ../../../modules/test-control/main.tf line 16, in resource "kubernetes_persistent_volume_claim_v1" "main":
09:52:35 │ 16: resource "kubernetes_persistent_volume_claim_v1" "main" {
09:52:35 │
09:52:35 │ The plugin encountered an error, and failed to respond to the
09:52:35 │ plugin.(*GRPCProvider).ValidateResourceConfig call. The plugin logs may
09:52:35 │ contain more details.
09:52:35 ╵
And then outputs the plugin crash stack (gist linked above)
Important Factoids
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