terraform-provider-vra VS terraform-provider-kubernetes

Compare terraform-provider-vra vs terraform-provider-kubernetes and see what are their differences.

Our great sponsors
  • Onboard AI - Learn any GitHub repo in 59 seconds
  • InfluxDB - Collect and Analyze Billions of Data Points in Real Time
  • SaaSHub - Software Alternatives and Reviews
terraform-provider-vra terraform-provider-kubernetes
2 6
91 1,504
- 0.2%
0.0 0.0
about 1 month ago 6 days ago
Go Go
Mozilla Public License 2.0 Mozilla Public License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.


Posts with mentions or reviews of terraform-provider-vra. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning terraform-provider-vra yet.
Tracking mentions began in Dec 2020.


Posts with mentions or reviews of terraform-provider-kubernetes. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-11-04.
  • Share a GPU between pods on AWS EKS
    10 projects | dev.to | 4 Nov 2021
    After the resources be provisioned, you might want to run terraform apply -refresh-only to refresh your local state as the creation of some resource change the state of others within AWS. Also, state differences on metadata.resource_version of k8s resources almost always show up after an apply. This seems to be related to this issue.
  • What are your experiences in using the Kubernetes and Helm Providers?
    2 projects | /r/Terraform | 6 Sep 2021
    We want to do that, but this issue has been a huge blocker for us. You might not hit it unless you’re using AKS, though.

What are some alternatives?

When comparing terraform-provider-vra and terraform-provider-kubernetes you can also consider the following projects:

azure-service-operator - Azure Service Operator allows you to create Azure resources using kubectl

terrajet - Generate Crossplane Providers from any Terraform Provider

k8s-device-plugin - NVIDIA device plugin for Kubernetes

asdf-tflint - An asdf plugin for installing terraform-linters/tflint.

asdf-hashicorp - HashiCorp plugin for the asdf version manager

aws-virtual-gpu-device-plugin - AWS virtual gpu device plugin provides capability to use smaller virtual gpus for your machine learning inference workloads

terraform-provider-ovirt - Terraform provider for oVirt 4.x

aws-eks-share-gpu - How to share the same GPU between pods on AWS EKS

k2tf - Kubernetes YAML to Terraform HCL converter

terraform-provider-grafana - Terraform Grafana provider

terraform-provider-kubectl - Terraform provider to handle raw kubernetes manifest yaml files

terraform-provider-aws - Terraform AWS provider [Moved to: https://github.com/hashicorp/terraform-provider-aws]