You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2025/03/18 16:39:00 UTC

[jira] [Updated] (FLINK-37504) Handle TLS Certificate Renewal

     [ https://issues.apache.org/jira/browse/FLINK-37504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated FLINK-37504:
-----------------------------------
    Labels: pull-request-available  (was: )

> 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)