[
https://issues.apache.org/jira/browse/FLINK-40857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gyula Fora closed FLINK-40857.
------------------------------
Fix Version/s: kubernetes-operator-1.17.0
Resolution: Fixed
merged to main f5456a4c8d59e28d89039d87ffc6c111c5445951
> 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
> Priority: Major
> Labels: pull-request-available
> Fix For: kubernetes-operator-1.17.0
>
>
> 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)
