[
https://issues.apache.org/jira/browse/FLINK-28649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gyula Fora closed FLINK-28649.
------------------------------
Fix Version/s: (was: kubernetes-operator-1.3.0)
Resolution: Won't Fix
This feature doesn't bring any real benefit to the user compared to manually
stopping the old job with a savepoint and creating a FlinkSessionJob CR
afterwards.
> Allow adopting unmanaged jobs as FlinkSessionJob resource
> ---------------------------------------------------------
>
> Key: FLINK-28649
> URL: https://issues.apache.org/jira/browse/FLINK-28649
> Project: Flink
> Issue Type: New Feature
> Components: Kubernetes Operator
> Reporter: Gyula Fora
> Priority: Major
>
> We should allow users to create a FlinkSessionJob resource for already
> existing jobs deployed to a managed session cluster.
> We should add a configuration option to specify the jobId of the running job,
> and then the operator would assume that it is running according to the
> initial spec provided.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
