Open aristosvo opened 1 month ago
I'm inclined to close this issue, as the underlying solution is available. It would be nice though to have a notification of the provider being memory deprived instead of just being killed, so I leave this open for @alexsomesan to judge whether we could somehow improve the error messaging
From Triage: Their may be a way to intercept the kill call regarding memory usage. Would require some investigation.
Hi @BBBmau 👋
Can you point me a bit in which direction to look? I have a bit of experience contributing to the Terraform providers for AWS and Azure, a pointer could help me do a bit of the work for you.
Terraform Version, Provider Version and Kubernetes Version
Affected Resource(s)
ExternalSecrets/v1beta1 SecretStore
viakubernetes_manifest
Terraform Configuration Files
Log output
Sometimes it is erroring out on
ReadResource
calls already, but always on the same calls in one run:Debug Output
I was caught by surprise that this error only generates a
Plugin did not respond
answer.Steps to Reproduce
Unsure, for certain runs this is the result while in other situations it works.
Expected Behavior
Consistent passing results or feedback about the issue at hand
Actual Behavior
Inconsistent results, most of the time failing, no feedback on the causing issue
Important Factoids
References
Community Note