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

Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2022/05/11 04:07:37 UTC

[GitHub] [flink-kubernetes-operator] wangyang0918 commented on pull request #199: [FLINK-27551] Update status manually instead of relying on updatecontrol

wangyang0918 commented on PR #199:
URL: https://github.com/apache/flink-kubernetes-operator/pull/199#issuecomment-1123160841

   I want to confirm what is the long term solution. Do we want to keep the manual status update or leverage the java-operator-sdk v3 to avoid the conflicts?
   
   The manual status update has a downside that the CR status could be inconsistent the real status. I think that is why we need the `statusCache` and have to update the CR status before every reconciliation. I just feel that it makes things more complicated. I know it also has the upside that we could update status in any time and do not need to re-trigger reconciliation. So I am not pretty sure which is the better one.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org