[FLINK-34177] Not able to create FlinkSessionJob in different namespace than flink deployment

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: kubernetes-operator-1.7.0
• Component/s: Kubernetes Operator

Environment

AWS EKS K8 version 1.25

Kubernetes Flink Operator 1.7.0{}

Flink 1.17/1.18

• Assignee: Unassigned
• Reporter: Pramod
• Created: 22/Jan/24 04:10
• Updated: 22/Jan/24 07:51
• Resolved: 22/Jan/24 07:51

Description

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 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 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.
 
Can someone confirm if Flink kubernetes operator supports Flink cluster(FlinkDeployment) to be in one namespace and then FlinkSessionJob in another namespace.??
Supporting multiple namespaces make my life a lot easier.
 
Note: Deploying FlinkSessionJob in the same namespace "Flink" works fine.