apache / apache/solr-operator

Consider adding a managed HorizontalPodAutoscaler

Open
#568 2 comments 2 reactions 0 assignees View on GitHub
autoscaling cloud
Dominant language
Go
Stars
283
Forks
148
PR merge metrics
No merged PRs in 30d

Description

Parent Ticket: https://github.com/apache/solr-operator/issues/536

Currently users can create their own HPA, and have it be used to control a `SolrCloud`'s `spec.replicas` parameter.

However if we want to support Autoscaling out-of-the-box, and make it as easy as possible for users to try, then it would be a good idea to add an optional managed HPA. This way users could use their custom HPA or use the built in.

There are many questions to be answered around the default properties of this HPA, and given that it would need to interact with the PrometheusExporter, things start to get a little iffy.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the parent ticket and the existing custom HPA path that controls SolrCloud's spec.replicas. Review how the PrometheusExporter would interact with a managed HPA; the work is done when the default HPA properties, optional managed behavior, and compatibility with user-provided HPAs are clearly designed and documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes, prometheus
Domain
devops, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.