[FLINK-30463] Stabilization period starts before job goes into RUNNING

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: kubernetes-operator-1.4.0
• Fix Version/s: kubernetes-operator-1.4.0
• Component/s: Kubernetes Operator
• Labels: pull-request-available
• Assignee: Maximilian Michels
• Reporter: Maximilian Michels
• Created: 20/Dec/22 11:57
• Updated: 23/Dec/22 17:08
• Resolved: 23/Dec/22 17:08

Description

We are tracking the stabilization period from the job start time which can greatly vary from the time the job goes into RUNNING state. This can result in no stabilization period at all leading to poor scaling decisions.

Thus, we should change the logic to use the update time in combination with a RUNNING job status.

Issue Links

• relates to: FLINK-30464 Metrics are collected in stabilization phase and do not always span a full metric window
• links to: GitHub Pull Request #492