monkey
karpenter-provider-aws
monkey | karpenter-provider-aws | |
---|---|---|
14 | 47 | |
2,370 | 5,902 | |
- | 2.7% | |
0.0 | 9.9 | |
almost 4 years ago | 1 day ago | |
Go | Go | |
GNU General Public License v3.0 or later | 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.
monkey
- Many reasons to always read the LICENSE
- GitHub is the trap that Microsoft if using to secretly and illegally read your code with total disrespect to its license, in order to train its AI to write better code and, eventually, make you redundant. Change my mind
-
looking for resources for learning unit testing in go?
Code that's hard to test is just bad code. And unlike most dynamic languages you can't just override some internals in Go (though there are some arcane hacks you can pull of but only at full moon https://github.com/bouk/monkey).
-
Library for monkey-patching functions
This person did not read the license of the original library https://github.com/bouk/monkey/blob/master/LICENSE.md
-
Alternative for Monkey patching
I am a new gopher. I was looking into the Monkey Patching module and it is archived now. I was wondering if there is an alternative for that.
-
Why go plugin addresses do not load with go binary
Here is an example of this in Go - but as he says, don't actually do this. https://github.com/bouk/monkey
-
is there an easy (python like way) to do mocks?
I discovered this lib a few days ago. https://github.com/bouk/monkey it allows you to monkey patch entire functions, replacing them by whatever you want. Perfect for mocking. It's simple to use. The program is hard patching the code using assembly to replace the function address at runtime. You should not use this lib out of your tests since it's absolutely not safe. It's only compatible with linux and windows. But it works great!
- Oops!
- Monkey Patching in Go (2015)
- I do not give anyone permissions to use this tool for any purpose. Don’t use it. I’m not interested in changing this license. Please don’t ask.
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.
What are some alternatives?
gomock - GoMock is a mocking framework for the Go programming language.
keda - KEDA is a Kubernetes-based Event Driven Autoscaling component. It provides event driven scale for any container running in Kubernetes
Mmock - Mmock is an HTTP mocking application for testing and fast prototyping
autoscaler - Autoscaling components for Kubernetes
rust-by-example - Learn Rust with examples (Live code editor included)
bedrock - Automation for Production Kubernetes Clusters with a GitOps Workflow
go-txdb - Immutable transaction isolated sql driver for golang
karpenterwebsite
timex - A test-friendly replacement for golang's time package [managed by soy-programador]
dapr - Dapr is a portable, event-driven, runtime for building distributed applications across cloud and edge.
gock - HTTP traffic mocking and testing made easy in Go ༼ʘ̚ل͜ʘ̚༽
camel-k - Apache Camel K is a lightweight integration platform, born on Kubernetes, with serverless superpowers