karpenter-provider-aws
openrasp
karpenter-provider-aws | openrasp | |
---|---|---|
47 | 1 | |
5,902 | 2,695 | |
3.1% | 0.9% | |
9.9 | 5.2 | |
3 days ago | 9 days ago | |
Go | C++ | |
Apache 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.
karpenter-provider-aws
- Karpenter
-
Stress testing Karpenter with EKS and Qovery
If you’re not familiar with Karpenter — watch my quick intro. But in a nutshell, Karpenter is a better node autoscaler for Kubernetes (say goodbye to wasted compute resources). It is open-source and built by the AWS team. Qovery is an Internal Developer Platform I’m a co-founder) that we’ll use to spin up our EKS cluster with Karpenter.
- Tortoise: Shell-Shockingly-Good Kubernetes Autoscaling
-
Five tools to add to your K8s cluster
Karpenter
-
Architecting for Resilience: Crafting Opinionated EKS Clusters with Karpenter & Cilium Cluster Mesh — Part 1
Here are a few reference links about the previous services and tools: What is Amazon EKS? Cluster Mesh Karpenter
- Scaling with Karpenter and Empty Pod(A.k.a Overprovisioning)
-
Reducing Cloud Costs on Kubernetes Dev Envs
Autoscaling over EKS can be accomplished using either the cluster-autoscaler project or Karpenter. If you want to use Spot instances, consider using Karpenter, as it has better integrations with AWS for optimizing spot pricing and availability, minimizing interruptions, and falling back to on-demand nodes if no spot instances are available.
-
Help required
Kubernetes has its own learning curve, but when tools like Karpenter exist it's kinda hard to beat for "auto-scaled compute" that is vendor agnostic. We leverage Karpenter for burst in our vSphere environment as well as our EC2 environment. Karpenter is invoking roughly the same Terraform code in both cases, just using different modules for the particular virtualization. Say we want to go to Azure and GCP -- we add an Azure and GCP module to the same Terraform codebase, and not much else needs to change from the "scale up / scale down" perspective.
-
Workload Operator. What do you think?
Also https://github.com/aws/karpenter/issues/331
-
Running Airflow task intensive Dags on Fargate.
Why don't you stick to the KubernetesPodOperator though? I fail to see a benefit in using the ECS operator considering you're already running Airflow in EKS. You can look into something like karpenter to manage your nodes.
openrasp
What are some alternatives?
keda - KEDA is a Kubernetes-based Event Driven Autoscaling component. It provides event driven scale for any container running in Kubernetes
dapr - Dapr is a portable, event-driven, runtime for building distributed applications across cloud and edge.
autoscaler - Autoscaling components for Kubernetes
wafw00f - WAFW00F allows one to identify and fingerprint Web Application Firewall (WAF) products protecting a website.
bedrock - Automation for Production Kubernetes Clusters with a GitOps Workflow
monkey - Monkey patching in Go
karpenterwebsite
overlord - Overlord是哔哩哔哩基于Go语言编写的memcache和redis&cluster的代理及集群管理功能,致力于提供自动化高可用的缓存服务解决方案。
heroku-buildpack-java - Heroku's buildpack for Java applications.
camel-k - Apache Camel K is a lightweight integration platform, born on Kubernetes, with serverless superpowers