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
Is this a BUG REPORT or FEATURE REQUEST?:
This is somewhere in between the two.
What happened:
When you try to check for the existence of a resource, the resource executor passes through the error directly from kubectl. I've filed an issue against kubernetes ( kubernetes/kubernetes#86042 ) because the get command returns an error when querying the singular if a resource doesn't exist.
What you expected to happen:
I should be able to get a response without the workflow step failing
How to reproduce it (as minimally and precisely as possible):
It should be a new flag/element under resource ignore-not-found : true and the default is false.
you are more welcome to create PR. Thanks for creating this issue.
Is this a BUG REPORT or FEATURE REQUEST?:
This is somewhere in between the two.
What happened:
When you try to check for the existence of a resource, the resource executor passes through the error directly from kubectl. I've filed an issue against kubernetes ( kubernetes/kubernetes#86042 ) because the get command returns an error when querying the singular if a resource doesn't exist.
What you expected to happen:
I should be able to get a response without the workflow step failing
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
I'm happy to try fixing it myself, just want to make sure we agree on the approach
Environment:
Other debugging information (if applicable):
The text was updated successfully, but these errors were encountered: