cloud-provider
cloud-provider defines the shared interfaces which Kubernetes cloud providers implement. These interfaces allow various controllers to integrate with any cloud provider in a pluggable fashion. Also serves as an issue tracker for SIG Cloud Provider. (by kubernetes)
cloud-provider-aws
Cloud provider for AWS (by kubernetes)
cloud-provider | cloud-provider-aws | |
---|---|---|
1 | 2 | |
227 | 353 | |
2.6% | 0.6% | |
9.0 | 8.7 | |
5 days ago | 4 days ago | |
Go | Go | |
Apache License 2.0 | Apache 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.
cloud-provider
Posts with mentions or reviews of cloud-provider.
We have used some of these posts to build our list of alternatives
and similar projects.
cloud-provider-aws
Posts with mentions or reviews of cloud-provider-aws.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-04.
-
k3s on AWS,does it make sense?
You can install the pod identity webhook and AWS cloud provider, csi provider etc on a bare kube cluster and get pretty close to the EKS experience. Not something I’d do for prod, but interesting as a learning exercise.
-
Blazing fast Kubernetes scaling with ASG warm pools
The most naïve way of implementing support for warm pools is to do nothing more than creating the warm pool. Unfortunately, this would start kubelet, which will register the Node with the cluster. Since the AWS cloud provider does not remove instances in stopped state, the control plane marks the Node NotReady, but keep it around in case it comes back up.
What are some alternatives?
When comparing cloud-provider and cloud-provider-aws you can also consider the following projects:
vsphere-csi-driver - vSphere storage Container Storage Interface (CSI) plugin