[
https://issues.apache.org/jira/browse/FLINK-30411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gyula Fora updated FLINK-30411:
-------------------------------
Fix Version/s: kubernetes-operator-1.4.0
> Flink deployment stuck in UPGRADING state when deploy flinkdeployment without
> resource
> --------------------------------------------------------------------------------------
>
> Key: FLINK-30411
> URL: https://issues.apache.org/jira/browse/FLINK-30411
> Project: Flink
> Issue Type: Bug
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-1.2.0, kubernetes-operator-1.3.0
> Reporter: tanjialiang
> Assignee: Kumar
> Priority: Major
> Labels: pull-request-available
> Fix For: kubernetes-operator-1.4.0
>
> Attachments: image-2022-12-14-17-22-12-656.png
>
>
> In flink kubernetes operator 1.2.0. When i deploy a flinkdeployments without
> resource, the flink deployment stuck in UPGRADING state.
> {code:java}
> apiVersion: flink.apache.org/v1beta1
> kind: FlinkDeployment
> metadata:
> name: socket-window-word-count
> spec:
> image: flink:1.16.0-scala_2.12-java8
> flinkVersion: v1_16
> flinkConfiguration:
> taskmanager.numberOfTaskSlots: "1"
> serviceAccount: flink
> job:
> jarURI: local:///opt/flink/examples/streaming/WordCount.jar
> parallelism: 2
> upgradeMode: stateless{code}
>
> when i kubectl describe flinkdeployments, i found this error message
> !image-2022-12-14-17-22-12-656.png!
>
> maybe we can validate it when apply flinkdeployment? When it is invalid,
> throw an error rather than apply flinkdeployment succeed.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)