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
While terraform-provider-google already added the option to turn on VPA option in google_container_cluster resource, terraform-provider-kubernetes still lacks support of VPA resources.
Currently our workaround to create VPA's is based on a module with .yaml templates and null_resource with local-exec.
@eddy-curv This resource actually isn't part of the Kubernetes API, it is actually a CRD that is created by this project. For the moment the provider doesn't support custom resources, but support is coming soon. See #215.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!
ghost
locked and limited conversation to collaborators
Jun 20, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
acknowledgedIssue has undergone initial review and is in our work queue.
Terraform Version
Terraform v0.12.2
Expected Behavior
Add support for vertical_pod_autoscaler resource
Actual Behavior
While terraform-provider-google already added the option to turn on VPA option in google_container_cluster resource, terraform-provider-kubernetes still lacks support of VPA resources.
Currently our workaround to create VPA's is based on a module with .yaml templates and null_resource with local-exec.
References
The text was updated successfully, but these errors were encountered: