
Security News
Deno 2.2 Improves Dependency Management and Expands Node.js Compatibility
Deno 2.2 enhances Node.js compatibility, improves dependency management, adds OpenTelemetry support, and expands linting and task automation for developers.
github.com/jthomperoo/custom-pod-autoscaler/v2
This project is supported by:
Custom Pod Autoscalers (CPAs) are custom Kubernetes autoscalers. This project is part of a framework that lets you quickly and easily build your own CPAs without having to deal with complex Kubernetes interactions using the tools and language of your choice.
This project is part of the Custom Pod Autoscaler Framework (CPAF) which is a set of tools to help you easily build your own CPAs. This project is the core of the CPAF, providing a program which runs inside your CPA to manage Kubernetes interactions and custom user logic interactions.
A Custom Pod Autoscaler can be created by using this project, extending the Docker base images provided and inserting your own logic; see the examples for more information.
Kubernetes provides the Horizontal Pod Autoscaler, which allows automatic scaling of the number of replicas in a resource (Deployment, ReplicationController, ReplicaSet, StatefulSet) based on metrics that you feed it. Mostly the metrics used are CPU/memory load, which is sufficient for most applications. You can specify custom metrics to feed into it through the metrics API also.
The limitation in the Horizontal Pod Autoscaler is that it has a hard-coded algorithm for assessing these metrics:
desiredReplicas = ceil[currentReplicas * ( currentMetricValue / desiredMetricValue )]
If you need more flexibility in your scaling, beyond this algorithm, Horizontal Pod Autoscaler doesn't meet your needs, you need to write your own scaling logic.
This project is a program that abstracts away complex Kubernetes interactions and handles interacting with custom user logic you can provide to determine how the autoscaler should operate.
When developing a Custom Pod Autoscaler you define logic for two stages:
These two pieces of logic are all the custom logic required to build a Custom Pod Autoscaler, the program will handle all Kubernetes API interactions for scaling/retrieving resources.
Check out this getting started guide for a quick start for developers.
See the wiki for more information, such as guides and references.
The Custom Pod Autoscaler Operator is the other part of the Custom Pod Autoscaler Framework, it is an operator that handles provisioning Kubernetes resources for your CPA.
See the contribution guidelines.
FAQs
Unknown package
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Deno 2.2 enhances Node.js compatibility, improves dependency management, adds OpenTelemetry support, and expands linting and task automation for developers.
Security News
React's CRA deprecation announcement sparked community criticism over framework recommendations, leading to quick updates acknowledging build tools like Vite as valid alternatives.
Security News
Ransomware payment rates hit an all-time low in 2024 as law enforcement crackdowns, stronger defenses, and shifting policies make attacks riskier and less profitable.