You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Matyas Orhidi (Jira)" <ji...@apache.org> on 2022/12/08 23:16:00 UTC
[jira] [Closed] (FLINK-29536) Add WATCH_NAMESPACES env var to kubernetes operator
[ https://issues.apache.org/jira/browse/FLINK-29536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matyas Orhidi closed FLINK-29536.
---------------------------------
Fix Version/s: kubernetes-operator-1.3.0
Resolution: Fixed
fixed via:
65b30d07da56259165936b5e0519f92640174cd6
686990a15db88789e538609e01a4dde73e966c12
> Add WATCH_NAMESPACES env var to kubernetes operator
> ---------------------------------------------------
>
> Key: FLINK-29536
> URL: https://issues.apache.org/jira/browse/FLINK-29536
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Affects Versions: kubernetes-operator-1.2.0
> Reporter: Tony Garrard
> Assignee: Tony Garrard
> Priority: Major
> Labels: pull-request-available
> Fix For: kubernetes-operator-1.3.0
>
>
> Provide the ability to set the namespaces watched by the operator using an env var. Whilst the additional config can still be used, the presence of the env var will take priority.
>
> Reasons for issue
> # Operator will take effect of the setting immediately as pod will roll (rather than waiting for the config to be refreshed)
> # If the operator is to be olm bundled we will be able to set the target namespace using the following
> {{ env:}}
> {{ - name: WATCHED_NAMESPACE}}
> {{ valueFrom:}}
> {{ fieldRef:}}
> {{ fieldPath: metadata.annotations['olm.targetNamespaces']}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)