Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support VerticalPodAutoscaler resource #718

Closed
eddy-curv opened this issue Dec 29, 2019 · 2 comments
Closed

Support VerticalPodAutoscaler resource #718

eddy-curv opened this issue Dec 29, 2019 · 2 comments
Labels
acknowledged Issue has undergone initial review and is in our work queue.

Comments

@eddy-curv
Copy link

eddy-curv commented Dec 29, 2019

Terraform Version

Terraform v0.12.2

  • provider.google v3.3.0
  • provider.google-beta v3.3.0
  • provider.kubernetes v1.9.0

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

@jrhouston jrhouston added the acknowledged Issue has undergone initial review and is in our work queue. label May 20, 2020
@jrhouston
Copy link
Collaborator

@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.

@ghost
Copy link

ghost commented Jun 20, 2020

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 ghost locked and limited conversation to collaborators Jun 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
acknowledged Issue has undergone initial review and is in our work queue.
Projects
None yet
Development

No branches or pull requests

2 participants