terraform-provider-kubernetes
azure-service-operator
Our great sponsors
terraform-provider-kubernetes | azure-service-operator | |
---|---|---|
6 | 6 | |
1,541 | 664 | |
1.2% | 3.8% | |
9.0 | 0.0 | |
3 days ago | 3 days ago | |
Go | Go | |
Mozilla Public License 2.0 | MIT License |
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-kubernetes
-
Does the kubernetes provider behave differently than other provider?
Now, to be honest, I'm not entirely sure/confident how this works. When I've used this kind of setup, I had two separate workspaces: one for setting up EKS and one for setting up Kubernetes within EKS. I'd apply the EKS workspace, first, then use its outputs for the Kubernete's workspace. You can see this pattern is specifically outlined in this EKS/k8s example. The Kubernetes provider docs also explicitly warns against creating the cluster in the same module as the Kubernetes provider. So it appears this may work, but it isn't recommended.
-
Name for move from Terraform to Kubernetes Operators
It is a pretty important distinction. Terraform and Kubernetes are fundamentally different in how they work. If you ever try to manage kubernetes state from terraform, it the differences become very obvious: https://github.com/hashicorp/terraform-provider-kubernetes/issues/1367
-
terraform-kubernetes-provider how to create secret from file?
I'm using the terraform kubernetes-provider and I'd like to translate something like this kubectl command into TF:
-
Share a GPU between pods on AWS EKS
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.
-
Kubernetes provider awfully trigger happy to delete entire state when it can't connect
You can open an issue here: https://github.com/hashicorp/terraform-provider-kubernetes/issues
-
What are your experiences in using the Kubernetes and Helm Providers?
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.
azure-service-operator
- Platform Engineering On Kubernetes
- Anyway to automate the AKS cluster creation using Yaml?
-
Kubernetes operator and CRDs for Azure ARM resources
Interesting! Seems similar to https://github.com/Azure/azure-service-operator
-
Kubernetes CRD/Operators for Azure resources
As per another comment below, MSFT does have a solution for this called the Azure service operator.
-
What are your experiences in using the Kubernetes and Helm Providers?
If I could start again I'd use ArgoCD + https://github.com/Azure/azure-service-operator to handle Azure based resources like postgres
What are some alternatives?
terrajet - Generate Crossplane Providers from any Terraform Provider
aws-controllers-k8s - AWS Controllers for Kubernetes (ACK) is a project enabling you to manage AWS services from Kubernetes
k8s-device-plugin - NVIDIA device plugin for Kubernetes
cloud-on-k8s - Elastic Cloud on Kubernetes
asdf-tflint - An asdf plugin for installing terraform-linters/tflint.
Pulumi - Pulumi - Infrastructure as Code in any programming language. Build infrastructure intuitively on any cloud using familiar languages 🚀
aws-virtual-gpu-device-plugin - AWS virtual gpu device plugin provides capability to use smaller virtual gpus for your machine learning inference workloads
theatre - GoCardless' collection of Kubernetes extensions
asdf-hashicorp - HashiCorp plugin for the asdf version manager
cluster-api - Home for Cluster API, a subproject of sig-cluster-lifecycle
terraform-provider-ovirt - Terraform provider for oVirt 4.x
cluster-api-provider-azure - Cluster API implementation for Microsoft Azure