gyfora commented on PR #749: URL: https://github.com/apache/flink-kubernetes-operator/pull/749#issuecomment-1892231646
@lajith2006 @tagarr I have been contemplating about this after reviewing the code and also read a bit more on the topic here: https://maelvls.dev/kubernetes-conditions/ To be honest I am not sure whether the current simplistic approach for representing a single status part (JobManagerDeplyomentStats / ResourceLifecycleState) makes too much sense. It doesn't really follow the semantics laid out by other Kubernetes resources like pod conditions etc. I think it would make sense to open a FLIP and properly design the conditions that we should represent instead of just adding this feature to "tick a box" -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
