Mate Czagany created FLINK-40857:
------------------------------------
Summary: Kubernetes Operator always replaces CR status 3 times on
reconciliation
Key: FLINK-40857
URL: https://issues.apache.org/jira/browse/FLINK-40857
Project: Flink
Issue Type: Bug
Components: Kubernetes Operator
Reporter: Mate Czagany
In StatusRecorder, there is a for-loop which hardens the status update in case
of intermittent connectivity issues, but the for loop keeps running even if the
update was successful.
A spec update between these updates would have then triggered a 409 error, and
the previous (successful) status update would have then triggered a
`StatusConflictException`:.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
