[
https://issues.apache.org/jira/browse/FLINK-27303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17524218#comment-17524218
]
Biao Geng commented on FLINK-27303:
-----------------------------------
Yeah, it seems that most generated configs are for constructing ClusterClient
to interact with the cluster.
Configs like templates, log configs or image configs that are for submission
will not be used by the operator's reconciliation.
We can build them only in submission methods.
Besides, it may also make sense to clear those temporary files for logs and
templates in {{FlinkDeploymentController#cleanup()}}.
> Flink Operator will create a large amount of temp log config files
> ------------------------------------------------------------------
>
> Key: FLINK-27303
> URL: https://issues.apache.org/jira/browse/FLINK-27303
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-1.0.0
> Reporter: Gyula Fora
> Priority: Critical
> Fix For: kubernetes-operator-1.0.0
>
>
> Now we use the configbuilder in multiple different places to generate the
> effective config including observer, reconciler, validator etc.
> The effective config gerenration logic also creates temporary log config
> files (if spec logConfiguration is set) which would lead to 3-4 files
> generated in every reconcile loop for a given job. These files are not
> cleaned up until the operator restarts leading to a large amount of files.
> I believe we should change the config generation logic and only apply the
> logconfig generation logic right before flink cluster submission as that is
> the only thing affected by it.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
