[
https://issues.apache.org/jira/browse/FLINK-27095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17518115#comment-17518115
]
Gyula Fora commented on FLINK-27095:
------------------------------------
Flink Application and Session clusters work very differently and have very
different lifecycles. It is not possible to run single jobs on an application
cluster or to submit and application job to a session cluster. (so re-using
resources is unfortunately not possible)
This is not a limitation of the operator but this is how flink works. These two
deployment modes have very little in common so the user would never want to
switch between them. Thus we should not allow it I think.
> Allow FlinkDeployment Mode Switching
> ------------------------------------
>
> Key: FLINK-27095
> URL: https://issues.apache.org/jira/browse/FLINK-27095
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Reporter: Usamah Jassat
> Priority: Major
> Fix For: kubernetes-operator-1.0.0
>
>
> Currently the operator doesn't allow switching the mode of an existing
> FlinkDeployment between Application and Session.
> I don't see why this shouldn't be allowed, if the mode is switched we should
> tear-down the cluster and spin-up a new cluster running in this new mode. It
> will add complexity into the connector but seems like a valid use-case.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
