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
Describe the bug
When multiple namespaces are specified using -n option, e.g. -n ns1 -n ns2, KRR iterates these namespaces inconsistently, sometimes skipping some namespaces. For example, it lists deployments for ns1 only and statefulsets for ns2 only.
I suppose this code should bind namespace variable early before lambda (not late inside), e.g.
Describe the bug
When multiple namespaces are specified using
-n
option, e.g.-n ns1 -n ns2
, KRR iterates these namespaces inconsistently, sometimes skipping some namespaces. For example, it listsdeployments
for ns1 only andstatefulsets
for ns2 only.I suppose this code should bind
namespace
variable early before lambda (not late inside), e.g.To Reproduce
Steps to reproduce the behavior:
Deployment
and oneStatefulSet
simple -n ns1
, you will see 2 recommendationssimple -n ns2
, you will see 2 recommendationssimple -n ns1 -n ns2
. I expect to see 4 recommendations, but in fact there will be less (e.g. only 2).The text was updated successfully, but these errors were encountered: