gke-policy-automation
gke-policy-automation copied to clipboard
Tool should not fail on a discovered cluster that does not exist
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Debug Output
N/A
Panic Output
N/A
Steps to Reproduce
- Create new GKE cluster
- Wait and ensure that GKE Cluster is visible in Assent Inventory
- Delete GKE cluster
- Run the tool
Expected Behavior
The tool produces warning. If there is more than one cluster to process, the remaining clusters are checked.
Actual Behavior
The tool produces an error and exists with system code 1. If there are multiple clusters to check, there is a high chance that not all of them will be processed.
References
N/A