terraform-provider-wireguard
terraform-provider-kubernetes
| terraform-provider-wireguard | terraform-provider-kubernetes | |
|---|---|---|
| 1 | 6 | |
| 15 | 1,541 | |
| - | 0.5% | |
| 6.0 | 9.0 | |
| 8 days ago | 5 days ago | |
| Go | Go | |
| Mozilla Public License 2.0 | Mozilla Public 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-wireguard
-
Ask HN: What is your Git rebase/commit/push flow?
By default it shows the commit message doesn't it? At least I'm not aware I've done anything for e.g. https://github.com/OJFord/terraform-provider-wireguard/actio...
The annoyance I'm describing is that when the commit message is 'merge branch master' (and especially if, as the label next to it shows, it is the master branch) this is crap and useless, and hiding the 'real' commits behind it that the committer had locally while behind the remote. If they had `git pull --rebase`d (or `git pull` with the config option set) the commit message would be that of the latest 'real' one.
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.
What are some alternatives?
terraform-provider-azurerm - Terraform provider for Azure Resource Manager
azure-service-operator - Azure Service Operator allows you to create Azure resources using kubectl
sublime_merge - Issue tracker for Sublime Merge
terrajet - Generate Crossplane Providers from any Terraform Provider
gitflow - Git extensions to provide high-level repository operations for Vincent Driessen's branching model.
k8s-device-plugin - NVIDIA device plugin for Kubernetes
gitupdate - Commit and push updated files with file names as commit message
asdf-tflint - An asdf plugin for installing terraform-linters/tflint.
git-gui - Tcl/Tk based UI for Git. I am currently acting as the project's maintainer.
aws-virtual-gpu-device-plugin - AWS virtual gpu device plugin provides capability to use smaller virtual gpus for your machine learning inference workloads
git-nomad - Synchronize work-in-progress git branches in a light weight fashion
asdf-hashicorp - HashiCorp plugin for the asdf version manager