You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flink.apache.org by "Gyula Fora (Jira)" <ji...@apache.org> on 2022/05/09 06:22:00 UTC

[jira] [Created] (FLINK-27551) Consider implementing our own status update logic

Gyula Fora created FLINK-27551:
----------------------------------

             Summary: Consider implementing our own status update logic
                 Key: FLINK-27551
                 URL: https://issues.apache.org/jira/browse/FLINK-27551
             Project: Flink
          Issue Type: Improvement
          Components: Kubernetes Operator
            Reporter: Gyula Fora


If a custom resource version is applied while in the middle of a reconcile loop (for the same resource but previous version) the status update will throw an error and re-trigger reconciliation.

In our case this might be problematic as it would mean we would retry operations that are not necessarily retriable and might require manual user intervention.

Please see: [https://github.com/java-operator-sdk/java-operator-sdk/issues/1198]

I think we should consider implementing our own status update logic that is independent of the current resource version to make the flow more robust.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)