Hi Gyula, Thank you and sorry for the late response.
My use case is that users may run finite jobs (either batch jobs or finite stream jobs), leaving a lot of deprecated flink deployments around. I’ve filed a ticket[1]. [1] https://issues.apache.org/jira/browse/FLINK-32143 Best, Paul Lam > 2023年5月15日 00:14，Gyula Fóra <gyula.f...@gmail.com> 写道： > > There is no such feature currently, Kubernetes resources usually do not > delete themselves :) > The problem I see here is by deleting the resource you lose all information > about what happened, you won't know if it failed or completed etc. > What is the use-case you are thinking about? > > If this is something you think would be good to add, please open a JIRA > ticket for it. But in any case this will probably merit a dev list discussion. > > Gyula > > On Sun, May 14, 2023 at 11:54 AM Paul Lam <paullin3...@gmail.com > <mailto:paullin3...@gmail.com>> wrote: > Hi all, > > Currently, if a job turns into terminated status (e.g. FINISHED or FAILED), > the flinkdeployment remains until a manual cleanup is performed. I went > through the docs but did not find any way to clean them up automatically. Am > I missing something? Thanks! > > Best, > Paul Lam
