gaoyan created FLINK-36403: ------------------------------ Summary: K8s native mode Use ConfigMap to get a better experience Key: FLINK-36403 URL: https://issues.apache.org/jira/browse/FLINK-36403 Project: Flink Issue Type: Improvement Components: Flink CDC Reporter: gaoyan
Currently, the operation of CDC's k8s native mode requires users to repackage the YAML into the Docker image each time to update the task, which is a poor experience. However, this issue can be resolved with a very simple method. When submitting a task, create a ConfigMap and write the YAML content into it, then mount it to the container. At the same time, there is no need to worry about resource release and deletion . The ConfigMap can be strongly bound to the container, and k8s will automatically handle these issues for us. If there are security concerns, we can also use a Secret. This method is simple and convenient, and does not require additional tools such as a k8s Operator. Regarding deployment, I also have some suggestions. There are many customizable parameters that can be configured for k8s native submissions. Currently, doing these things only through CLI args is very difficult for users. Writing them into the YAML for configuration will provide a better experience, as shown below: {code:java} source: xxxxx sink: xxxxxx pipeline: xxxx deploy: target: k8s-native jar: "/opt/cdc/cdc.jar" namespace: account: xxxxxxxx{code} Would this approach be more user-friendly? I have done similar things in other communities. If the CDC community thinks this idea is feasible, I am willing to work on this issue and submit a PR. -- This message was sent by Atlassian Jira (v8.20.10#820010)