search

GoogleCloudPlatform / flink-on-k8s-operator

[DEPRECATED] Kubernetes operator for managing the lifecycle of Apache Flink and Beam applications.
Apache License 2.0
659 stars 265 forks source link

Not able to deploy the operator to watch particular namesapce #341

Open navneet066 opened 4 years ago

navneet066 commented 4 years ago

In the process of the evaluation of the Flink K8S Operator, We wanted to check the Watch Namespace functionality of the operator. But seems like after deploying the Operator with --set watchNamespac parameter, It is happening in the whole cluster.

Command Used:

helm install -g  ./helm-chart/flink-operator/ --set operatorImage.name=gcr.io/flink-operator/flink-operator:latest --set flinkOperatorNamespace=flink-test --set watchNamespace=flink-watch-ns

According to the above command (As per the documentation) it should only monitor the resources in flink-watch-ns, but still, We are able to deploy Job Cluster or Session Cluster in all the namespaces of the cluster.

Please let us know if we are missing any steps or there is any related bug.

Note: We are using the code from the master branch.

guruprasathT commented 4 years ago

Yes it is absolutely possible. But unfortunately the current helm chart may need additional changes to separate namespace (with respective SA) and cluster level deployment chart.