aws-ami-gpu-monitoring
This project contains the code necessary to build an AWS AMI with monitoring capabilities of GPU usage (among other metrics) using CloudWatch. (by DanielKneipp)
terraform-provider-kubernetes
Terraform Kubernetes provider (by hashicorp)
Our great sponsors
aws-ami-gpu-monitoring | terraform-provider-kubernetes | |
---|---|---|
1 | 6 | |
3 | 1,541 | |
- | 1.2% | |
3.2 | 9.0 | |
over 2 years ago | 4 days ago | |
HCL | Go | |
MIT License | 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.
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.
aws-ami-gpu-monitoring
Posts with mentions or reviews of aws-ami-gpu-monitoring.
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
From that repo, the only thing changed is the base AMI, which in this case an AMI tailored for accelerated hardware on EKS was used. The list of compatible AMIs for EKS can be obtained in this link updated regularly by AWS. Also, the AMI from AWS comes with SSM agent in it, so no need to change anything regarding that.
terraform-provider-kubernetes
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.
-
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?
When comparing aws-ami-gpu-monitoring and terraform-provider-kubernetes you can also consider the following projects:
aws-eks-share-gpu - How to share the same GPU between pods on AWS EKS
azure-service-operator - Azure Service Operator allows you to create Azure resources using kubectl
k8s-device-plugin - NVIDIA device plugin for Kubernetes
terrajet - Generate Crossplane Providers from any Terraform Provider
asdf-tflint - An asdf plugin for installing terraform-linters/tflint.
k2tf - Kubernetes YAML to Terraform HCL converter
containers-roadmap - This is the public roadmap for AWS container services (ECS, ECR, Fargate, and EKS).
aws-virtual-gpu-device-plugin - AWS virtual gpu device plugin provides capability to use smaller virtual gpus for your machine learning inference workloads
asdf-hashicorp - HashiCorp plugin for the asdf version manager
aws-ami-gpu-monitoring vs aws-eks-share-gpu
terraform-provider-kubernetes vs azure-service-operator
aws-ami-gpu-monitoring vs k8s-device-plugin
terraform-provider-kubernetes vs terrajet
aws-ami-gpu-monitoring vs asdf-tflint
terraform-provider-kubernetes vs k8s-device-plugin
aws-ami-gpu-monitoring vs k2tf
terraform-provider-kubernetes vs asdf-tflint
aws-ami-gpu-monitoring vs containers-roadmap
terraform-provider-kubernetes vs aws-virtual-gpu-device-plugin
aws-ami-gpu-monitoring vs aws-virtual-gpu-device-plugin
terraform-provider-kubernetes vs asdf-hashicorp