We’re excited to announce the open beta of the New Relic Horizontal Pod autoscaler.
The Horizontal Pod Autoscaling (HPA) feature, which was introduced in Kubernetes v1.2, allows users to autoscale their applications off of basic metrics like CPU, accessed from a resource called metrics-server.
With Kubernetes v1.6, it became possible to autoscale off of user-defined custom external metrics collected from within the cluster.
Support for external metrics was introduced in Kubernetes v1.10, which allows users to autoscale off of any metric from outside the cluster.
- You don’t need anymore dedicated resources to manually add or remove pods based on your real-time demands.
- Longer uptime by better handling of traffic spikes.
- More economical solution in comparison with allocating a fixed number of pods.
- The New Relic metric adapter will automatically autoscale your Kubernetes cluster based on any metrics gathered from your applications or any infrastructure service like the number of requests received per second by a web server.
How it works?
Our metric adapter gets the metric value from the NR NerdGraph API based on a NRQL query then this value is submitted to the Kubernetes external metrics API. Thanks to that, the Horizontal Pod Autoscaler is ready to scale the cluster based on an external metric.
Get started with the New Relic Metrics adapter
New Relic Metric Adapter is only available for Kubernetes v1.16 and above. To see the list full of requirements check the following link.
By using Helm charts any New Relic user can easily install our Kubernetes integration with HPA or simply update it to enable the NR metric adapter.
More information about the installation process here.
Contribute to our New Relic Metrics adapter
From New Relic we’re fully compromised with the open source community, check our public repo to provide us feedback, contributions or any proposal you may consider.