temporalio / temporalio/temporal-worker-controller
[Feature Request] Support Watermark Pod Autoscaler (WPA)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 187
- Forks
- 70
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 31
Description
Is your feature request related to a problem? Please describe.
The WPA scaler is similar to HPA in its spec, however there is a small field name difference for matchLabels:
HPA: spec.metrics[*].external.metric.selector.matchLabels
WPA: spec.metrics.external.metricSelector.matchLabels
This is blocking Datadog from using WPA with the WorkerResourceTemplate to scale workers.
Describe the solution you'd like
Support the WPA path to populate the matchLabels with the injected values in WRTs.
(Or optionally, a more general solution would be to support matchLabel detection for anything below spec.metrics.)
Contributor guide
No contributing guide indexed for this repository
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 by locating the WorkerResourceTemplate logic that injects values into spec.metrics and the existing HPA matchLabels handling. Compare that path with the WPA metricSelector path described in the issue; done means WPA matchLabels are populated for worker scaling without breaking HPA behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100