terraform-provider-kubectl
terrajet
terraform-provider-kubectl | terrajet | |
---|---|---|
1 | 3 | |
553 | 289 | |
- | - | |
0.0 | 7.7 | |
3 months ago | over 1 year ago | |
Go | Go | |
Mozilla Public License 2.0 | Apache License 2.0 |
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.
terraform-provider-kubectl
-
Weekly: This Week I Learned (TWIL?) thread
We ended up switching to terraform-provider-kubectl (https://github.com/gavinbunney/terraform-provider-kubectl) which solved this problem entirely 😊✨
terrajet
-
`Depends_on` in Terraform Providers
And to my personal opinion they would've better spent some resources to contribute to the target providers instead of embedding or directly code-generating (https://github.com/crossplane/terrajet) from Terraform. Spreading the efforts and resources doesn't really help that much with the existing Terraform issues.
So, I find both pulumi and crossplane rather parasitic for the existing Terraform Provider Infrastructure. Actually fixing the bicycle would've been better than strapping a jet engine on top.
For me, this situation is very similar to the long resolved issue with docker multistage... with myriads of CLI tools on top obsoleting in result.
-
Deep Dive: Terraform in Kubernetes – 1000s of CRDs
We have implemented Terrajet (https://github.com/crossplane/terrajet) that generates CRDs that's completely compliant with Kubernetes Resource Model; references, label selectors, spec/status, no TF state blob saved anywhere.
Check it out!
-
How to apply gitops workflow with Vault and Kubernetes?
Crossplane comes to my mind when thinking of using the GitOps way to provision infrastructures. Unfortunately, I think there isn't a Vault Crossplane provider at the moment but there's a terrajet project that allows you to generate Crossplane providers from Terraform providers. Might be a long shot and seems overly complex for a use-case like yours, but worthwhile if you plan to let ArgoCD manage everything.
What are some alternatives?
terraform-provider-kubernetes - Terraform Kubernetes provider
terraform-provider-helm - Terraform Helm provider
universal-crossplane - Enterprise-grade @crossplane from @upbound
terraform-provider-kubernetes - Terraform Kubernetes provider [Moved to: https://github.com/hashicorp/terraform-provider-kubernetes]
terraform-provider-carvel - Carvel Terraform provider with resources for ytt and kapp to template and deploy to Kubernetes
terraform-provider-aws - Terraform AWS provider [Moved to: https://github.com/hashicorp/terraform-provider-aws]
provider-jet-aws - AWS Provider for Crossplane that is built with Terrajet.
atlantis - Terraform Pull Request Automation
crossplane - The Cloud Native Control Plane
consul-terraform-sync - Consul Terraform Sync is a service-oriented tool for managing network infrastructure near real-time.