Hi everyone, I would like to kick off a discussion on refactoring the existing Kubernetes resources construction architecture design.
I created a design document [1] that clarifies our motivation to do this and some improvement proposals for the new design. Briefly, we would like to 1. Introduce a unified monadic-step based orchestrator architecture that has a better, cleaner and consistent abstraction for the Kubernetes resources construction process, both applicable to the client side and the master side. 2. Add some dedicated tools for centrally parsing, verifying, and managing the Kubernetes parameters. It would be great to start the efforts before adding big features for the native Kubernetes submodule, and Tison and I plan to work together for this issue. Please let me know your thoughts. Regards, Canbin Zheng [1] https://docs.google.com/document/d/1dFBjqho8IRyNWxKVhFnTf0qGCsgp72aKON4wUdHY5Pg/edit?usp=sharing [2] https://issues.apache.org/jira/browse/FLINK-16194
