In HA mode the configMap will be retained after deletion of the deployment: https://ci.apache.org/projects/flink/flink-docs-master/docs/deployment/ha/kubernetes_ha/ ( Refer High availability data clean up)
On Fri, Oct 22, 2021 at 8:13 AM Yangze Guo <karma...@gmail.com> wrote: > For application mode, when the job finished normally or be canceled, > the ConfigMaps will be cleanup. > For session mode, when you stop the session through [1], the > ConfigMaps will be cleanup. > > [1] > https://ci.apache.org/projects/flink/flink-docs-release-1.13/docs/deployment/resource-providers/native_kubernetes/#stop-a-running-session-cluster > > Best, > Yangze Guo > > On Thu, Oct 21, 2021 at 6:37 AM Weiqing Yang <yangweiqing...@gmail.com> > wrote: > > > > > > Hi, > > > > Per the doc, `kubernetes.jobmanager.owner.reference` can be used to set > up the owners of the job manager Deployment. If the owner is deleted, then > the job manager and its related pods will be deleted. How about the HA > related ConfigMaps? Are they also deleted when deleting the owner of the > job manager Deployment? Per the wiki here, the HA data will be retained > when deleting jobmanager Deployment. If we want to delete these HA related > configMaps as well when deleting the job manager, what is the suggested way > to do that? > > > > Thanks, > > weiqing > > >
