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

Gyula Fora closed FLINK-33763.
------------------------------
    Fix Version/s: kubernetes-operator-1.8.0
       Resolution: Fixed

merged to main 9e8dcd97cd07d4b769997ce40e43047301886c41

> Support manual savepoint redeploy for jobs and deployments
> ----------------------------------------------------------
>
>                 Key: FLINK-33763
>                 URL: https://issues.apache.org/jira/browse/FLINK-33763
>             Project: Flink
>          Issue Type: New Feature
>          Components: Kubernetes Operator
>            Reporter: Gyula Fora
>            Assignee: Gyula Fora
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: kubernetes-operator-1.8.0
>
>
> A common request is to support a streamlined, user friendly way of 
> redeploying from a target savepoint.
> Previously this was only possible by deleting the CR and recreating it with 
> initialSavepointPath. A big downside of this approach is a loss of 
> savepoint/checkpoint history in the status that some platforms may need, 
> resulting in non-cleaned up save points etc.
> We suggest to introduce a `savepointRedeployNonce` field in the job spec 
> similar to other action trigger nonces.
> If the nonce changes to a new non null value the job will be redeployed from 
> the path specified in the initialSavepointPath (or empty state If the path is 
> empty)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to