[
https://issues.apache.org/jira/browse/FLINK-37504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17937315#comment-17937315
]
Gabor Somogyi commented on FLINK-37504:
---------------------------------------
Since this impacts hearth of the whole authentication logic of Flink I would
suggest also to write a FLIP about it.
I'm the author of the code in the operator where it's copied from so I know
what's going on, but the impact is heavy and would be good to show the
internals with others. In general I'm +1 with the direction.
> Handle TLS Certificate Renewal
> ------------------------------
>
> Key: FLINK-37504
> URL: https://issues.apache.org/jira/browse/FLINK-37504
> Project: Flink
> Issue Type: Improvement
> Reporter: Nicolas Fraison
> Priority: Minor
> Labels: pull-request-available
>
> Flink does not reload certificate if underlying truststore and keytstore are
> updated.
> We aim at using 1 day validity certificate which currently means having to
> restart our jobs every day.
> In order to avoid this we will need to add a feature to be able to reload TLS
> certificate when underlying truststore and keytstore are updated
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
