[FLINK-34619] Do not wait for scaling completion in UPGRADE state with in-place scaling

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: kubernetes-operator-1.7.0
• Fix Version/s: kubernetes-operator-1.8.0
• Component/s: Kubernetes Operator
• Labels: pull-request-available
• Release Note: Merged via 8938658ed245545e6436ff22cbb8b2fabd4047f1
• Assignee: Gyula Fora
• Reporter: Gyula Fora
• Created: 07/Mar/24 13:04
• Updated: 14/Mar/24 14:29
• Resolved: 14/Mar/24 14:29

Description

The operator currently puts the resource into upgrading state after triggering in-place scaling and keeps observing until the desired parallelism is reached before moving to deployed / stable. 

However this means that due to how the adaptive scheduler works this parallelism may never be reached and this is expected.

We should simplify the logic to consider scaling "done" once the resource requirements have been set correctly and then leave the rest to the adaptive scheduler

Issue Links

• links to: GitHub Pull Request #793