lyft / lyft/flinkk8soperator

Scaling Orchestration

Open
#146 6 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
581
Forks
153
PR merge metrics
No merged PRs in 30d

Description

Hi,

I have a question regarding scaling the parallelism value.

For now, we are doing the manual way, whereby we edit the FlinkApplication YAML to change the parallelism value, apply the YAML, and let the operator transition from the old job cluster to the newly created job cluster.

Is there any recommended way to automatically orchestrate the above, similar to how HPA works in K8S, whereby HPA will kick in once the metrics exceed a certain value?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing how the operator handles FlinkApplication YAML changes and transitions from an old job cluster to a newly created one. Compare that flow with Kubernetes HPA behavior and determine the metrics, scaling trigger, and orchestration scope required for automatic parallelism changes.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.