provide custom metrics APIService
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11.5k
- Forks
- 1.4k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 53
Description
Summary
Kubernetes provides a Horizontal Pod Autoscaler to enable scaling pods based on metrics. These metrics may come from the container (cpu, mem), or, via a custom metrics APIService.
The autoscaling thanos-demo demonstrates using a k8s-prometheus-adapter to read Linkerd latency metrics, expose them via a custom metrics APIService, and affect scaling via an HPA.
Proposal
Implement a custom metrics API service in Linkerd's control-plane. This would enable autoscaling out-of-the-box, and also enable Linkerd's metrics to be easily consumable via systems that expect Kubernetes metrics.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Kubernetes Horizontal Pod Autoscaler and custom metrics APIService documentation, then review the autoscaling thanos-demo and k8s-prometheus-adapter referenced in the issue. Define how Linkerd latency metrics will be exposed by the control plane and consumed as Kubernetes custom metrics; done means autoscaling can use those metrics without an external adapter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- api, backend, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100