Hi all, I am deploying a Flink Cluster in session mode using Kubernetes HA and have seen it working with the different config maps for the dispatcher, restserver and resourcemanager. I also have configured storage for checkpointing and HA metadata.
When I submit a job, I can see that a config map is created for it containing checkpoint information which is updated correctly. Yet, when I cancel a job I assume the config map would be deleted but it's seems that it isn't. Is this the intended behaviour? I am worried that s many jobs are submitted and cancelled from Flink Cluster a large number of Config Maps would remain in the cluster. Thanks in advance, Enrique -- Sent from: http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/
