http-add-on
macrome
Our great sponsors
http-add-on | macrome | |
---|---|---|
9 | 2 | |
290 | 7 | |
4.1% | - | |
8.6 | 0.0 | |
7 days ago | about 2 years ago | |
Go | TypeScript | |
Apache License 2.0 | MIT License |
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.
http-add-on
-
Autoscaling Ingress controllers in Kubernetes
KEDA ships with an HTTP add-on to enable HTTP scaling.
-
Request-based autoscaling in Kubernetes: scaling to zero
KEDA has a special scaler that creates an HTTP proxy that measures and buffers requests before they reach the app.
- How to descale to zero?
-
Ask HN: Who Wants to Collaborate?
I am a core maintainer on the KEDA HTTP Addon project (https://github.com/kedacore/http-add-on). It's 100% written in Go and we are a small group looking for additional contributors. I believe there are interesting challenges ahead of us that will be enjoyable to solve.
If you're interested, please reach out. My username here is the same as my username on the Gophers and Kubernetes slack groups.
(You're of course welcome to just go pick up an issue in the repo if you'd prefer)
-
Synchronizing the KEDA HTTP Addon Request Routing Table Across Hundreds of Interceptor Pods
The KEDA HTTP Addon project contains three major components: the operator, scaler and interceptor.
-
Fan-in / Fan-out with Go
Hacking on the KEDA HTTP Addon, I found myself having to do something familiar:
- Ask r/kubernetes: What are you working on this week?
-
Next Steps for KEDA HTTP
First, we need to finish the minimal infrastructure. The components and supporting artifacts (Helm charts, CI scripts, etc...) are being built in PR #2, and once we have them completed, we will merge it [5]. Second, we need to establish a roadmap. We're beginning to outline it now and will finish it shortly after merging.
macrome
-
Ask HN: Who Wants to Collaborate?
This is related to the goals I have for https://github.com/conartist6/macrome, except that my focus is on restoring forking potential for frontend development.
I expect if forks become more abundant that the need for trust will be a major driver of merges.
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
chessmadra-frontend
k8s-image-swapper - Mirror images into your own registry and swap image references automatically.
go-littr - Link aggregator inspired by (old)reddit using ActivityPub federation. (mirror repository) [Moved to: https://github.com/mariusor/brutalinks]
relevant_xkcd - A reccomender engine for relavent xkcd comics
DevUtils-app - All-in-one Toolbox for Developers. Native macOS app.
dbench - Benchmark Kubernetes persistent disk volumes with fio: Read/write IOPS, bandwidth MB/s and latency
rsyscall - Process-independent interface to Linux system calls
Yacy - Distributed Peer-to-Peer Web Search Engine and Intranet Search Appliance
fhir-works-on-aws-deployment - A serverless implementation of the FHIR standard that enables users to focus more on their business needs/uniqueness rather than the FHIR specification
platelet - Dispatch system for emergency volunteer couriers.