Code of Conduct
Search before asking
Describe the proposal
Due to many issues with the current version of StreamPark Flink on Kubernetes in terms of submitting and tracking tasks, we hope to refactor the entire module based on the Flink Kubernetes Operator to better address the following problems:
- Inaccurate and confusing tracking of Flink on Kubernetes status;
- Unstable and lengthy Flink K8s Application Job submission process;
- Scattered Event Watcher thread pool code;
Resources
Task list
Dependency relationship of subtasks
#2880 → #2881 → #2882, #2883, #2884, #2885 → #2887
Are you willing to submit PR?
Code of Conduct
Search before asking
Describe the proposal
Due to many issues with the current version of StreamPark Flink on Kubernetes in terms of submitting and tracking tasks, we hope to refactor the entire module based on the Flink Kubernetes Operator to better address the following problems:
Resources
Task list
Dependency relationship of subtasks
#2880 → #2881 → #2882, #2883, #2884, #2885 → #2887
Are you willing to submit PR?