You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Specifying a namespaceSelector under triggerGroups for an EventListener should create an event listener pod with with the --is-multi-ns flag set to true.
Actual Behavior
When a namespaceSelector under triggerGroups for an EventListener is specified without additionally specifying a namespaceSelector under spec the pod is created with --is-multi-ns=false.
Steps to Reproduce the Problem
With the following manifests in is-multi-ns-false.yaml...
With a namespaceSelector under spec set to match a non-existent namespace the pod is configured to inspect namespaces and the namespaceSelectors under triggerGroups works as expected. The namespaceSelector under spec will not match anything so there will be no duplicates. A temporary fix for people who encounter the same problem. (Assuming the maintainers agree it is a problem.)
Additional Info
Kubernetes version:
Output of kubectl version:
Client Version: v1.28.2
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.27.6
Expected Behavior
Specifying a
namespaceSelector
undertriggerGroups
for anEventListener
should create an event listener pod with with the--is-multi-ns
flag set totrue
.Actual Behavior
When a
namespaceSelector
undertriggerGroups
for anEventListener
is specified without additionally specifying anamespaceSelector
underspec
the pod is created with--is-multi-ns=false
.Steps to Reproduce the Problem
With the following manifests in
is-multi-ns-false.yaml
...Run the following...
With the following manifests in
is-multi-ns-true.yaml
...Run the following...
With a
namespaceSelector
underspec
set to match a non-existent namespace the pod is configured to inspect namespaces and thenamespaceSelector
s undertriggerGroups
works as expected. ThenamespaceSelector
underspec
will not match anything so there will be no duplicates. A temporary fix for people who encounter the same problem. (Assuming the maintainers agree it is a problem.)Additional Info
Kubernetes version:
Output of
kubectl version
:The text was updated successfully, but these errors were encountered: