You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Gyula Fora (Jira)" <ji...@apache.org> on 2024/01/22 07:51:00 UTC
[jira] [Commented] (FLINK-34177) Not able to create FlinkSessionJob in different namespace than flink deployment
[ https://issues.apache.org/jira/browse/FLINK-34177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17809280#comment-17809280 ]
Gyula Fora commented on FLINK-34177:
------------------------------------
Flink session jobs need to be created in the same namespace as the corresponding FlinkDeployment. This is an intentional limitation at the moment.
> Not able to create FlinkSessionJob in different namespace than flink deployment
> -------------------------------------------------------------------------------
>
> Key: FLINK-34177
> URL: https://issues.apache.org/jira/browse/FLINK-34177
> Project: Flink
> Issue Type: Bug
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-1.7.0
> Environment: *AWS EKS K8 version 1.25*
> {*}Kubernetes Flink Operator 1.7.0{*}{*}{*}
> *Flink 1.17/1.18*
> Reporter: Pramod
> Priority: Major
>
> Here is my use case:
> 1) I created a namespace "flink" in aws cluster with k8 version 1.25
> 2) Deployed flink kubernetes operator in "flink" namespace using helm chart
> 3) deployed FlinkDeployment similar to [flink-kubernetes-operator/examples/basic-session-deployment-only.yaml at main · apache/flink-kubernetes-operator · GitHub|https://github.com/apache/flink-kubernetes-operator/blob/main/examples/basic-session-deployment-only.yaml] in flink namespace
> 4) Then deployed FlinkSession job similar to [flink-kubernetes-operator/examples/basic-session-job-only.yaml at main · apache/flink-kubernetes-operator · GitHub|https://github.com/apache/flink-kubernetes-operator/blob/main/examples/basic-session-job-only.yaml] but in different namespace "tss"
> 5) Already added both the namespaces to watchednamespaces
> watchNamespaces: ["tss", "flink"]
>
> Expected:
> FlinkSessionJob will start in tss namespace
>
> Actual:
> Job is not starting and throwing the error "*Flink version null is not supported by this operator version*"
>
>
>
>
> My suspect is it seems FlinkDeployment and FlinkSessionJob should be in the namespace. However i am not sure. So i am raising this bug.
>
> {color:#FF0000}*Can someone confirm if Flink kubernetes operator supports Flink cluster(FlinkDeployment) to be in one namespace and then FlinkSessionJob in another namespace.??*{color}
> Supporting multiple namespaces make my life a lot easier.
>
> Note: Deploying FlinkSessionJob in the same namespace "Flink" works fine.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)