karpenter-provider-aws
cdk8s
karpenter-provider-aws | cdk8s | |
---|---|---|
47 | 48 | |
5,902 | 4,138 | |
3.1% | 1.3% | |
9.9 | 9.7 | |
3 days ago | 6 days ago | |
Go | JavaScript | |
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.
cdk8s
-
K8s Service Meshes: The Bill Comes Due
Any, it doesn’t matter which as long as you don’t have to count spaces in yaml by hand.
If you really want a concrete recommendation try https://cdk8s.io/.
- Why the fuck are we templating YAML? (2019)
- Cdk8s: Kubernetes native apps and abstractions using object-oriented programming
-
10 Ways for Kubernetes Declarative Configuration Management
CDK8s - CDK8s is used to define Kubernetes resources and applications. CDK8s uses the high-level abstraction concept called constructs to represent various Kubernetes resources such as deployments, services, and configurations. Developers can write code in programming languages like TypeScript, Python, and Java, and CDK8s will translate this code into standard Kubernetes YAML manifests that can be directly applied to a Kubernetes cluster.
-
I built a React renderer for Kubernetes configurations
Have you looked into https://cdk8s.io/? I've been using it for a while now, and I must admit TypeSript does help a lot. Not really sold on your React syntax yet, but well done nevertheless
-
How are most EKS clusters deployed?
I, personally, prefer to wrap it in CDKTF/CDK8S in golang and manage with Crossplane Composition Functions, but your mileage may vary. I'm finding way too bugs in CDK's... but it calms me a bit, that Amazon folks actually looking into it.
-
Editing Badly formatted yaml file
Have you looked into cdk8s? That will let you get away from dealing with yaml and let you use code instead. Helm included.
-
kpt, cue, ... Your experiences?
My favorite is cdk8s + typescript.
- Cloud Development Kit for Kubernetes
-
Dump Kustomize with 20 lines of TypeScript
What about https://cdk8s.io/?
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
helmfile - Deploy Kubernetes Helm Charts
autoscaler - Autoscaling components for Kubernetes
Pulumi - Pulumi - Infrastructure as Code in any programming language. Build infrastructure intuitively on any cloud using familiar languages 🚀
bedrock - Automation for Production Kubernetes Clusters with a GitOps Workflow
terraform-cdk - Define infrastructure resources using programming constructs and provision them using HashiCorp Terraform
karpenterwebsite
aws-cdk - The AWS Cloud Development Kit is a framework for defining cloud infrastructure in code
dapr - Dapr is a portable, event-driven, runtime for building distributed applications across cloud and edge.
jsonnet - Jsonnet - The data templating language
camel-k - Apache Camel K is a lightweight integration platform, born on Kubernetes, with serverless superpowers
kubernetes-the-hard-way - Bootstrap Kubernetes the hard way. No scripts.