Bug: namespace-scoped agent could not deploy operator with "Namespace" set to a different namespace in the yaml file #3915
Assignees
Labels
Comments
LiilyZhang
added a commit
to LiilyZhang/anax
that referenced
this issue
Oct 4, 2023
…y operator with 'Namespace' set to a different namespace in the yaml file Signed-off-by: Le Zhang <[email protected]>
LiilyZhang
added a commit
to LiilyZhang/anax
that referenced
this issue
Oct 6, 2023
…y operator with 'Namespace' set to a different namespace in the yaml file Signed-off-by: Le Zhang <[email protected]>
LiilyZhang
added a commit
to LiilyZhang/anax
that referenced
this issue
Oct 6, 2023
…y operator with 'Namespace' set to a different namespace in the yaml file Signed-off-by: Le Zhang <[email protected]>
LiilyZhang
added a commit
to LiilyZhang/anax
that referenced
this issue
Oct 6, 2023
…y operator with 'Namespace' set to a different namespace in the yaml file Signed-off-by: Le Zhang <[email protected]>
LiilyZhang
added a commit
that referenced
this issue
Oct 9, 2023
Issue #3915 - Bug: namespace-scoped agent could not deplo…
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If resources (role, rolebinding, ....) yaml has a
Namespacedefined but is different from the namespace that agent is in, namespace-scoped agent failed deploy it because of conflict.The text was updated successfully, but these errors were encountered: