gyfora commented on PR #384: URL: https://github.com/apache/flink-kubernetes-operator/pull/384#issuecomment-1257587740
On a very high level I agree with you @morhidi and the `ResourceLifecycleState` helper serves a related purpose. Unfortunately I feel that there are so many corner cases and slightly different deployment scenarios that a purely state machine based approach would have waaaay too many states and many of these would be hard to name or abstract properly. Even in the best case I think we would end up with a mix of a better state machine represenation + extra status info to capture some cornercases. While the status at the moment contains a quite a lot of different types of information, at least it is somewhat normalized. It would be great to see what kind of state machine you have in mind, maybe there is a nice way to simplify this. -- 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]
