-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Warn instead of panic when API resource not found or forbidden #73
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Before this fix, we were doing log.Info().Err(err), which emits a one-line log that is both info and error: {"level":"info","error":"resource not found","namespace":"demo2","time":"2023-07-24T15:23:17+02:00","message":"no pre-existing PolicyReport, will create one at the end of the scan"} Signed-off-by: Víctor Cuadrado Juan <[email protected]>
We are looking for namespaced resources, clusterwide resources get checked in getClusterWideResourcesForPolicies() Signed-off-by: Víctor Cuadrado Juan <[email protected]>
When policies are configured with a spec.rules GVK, if resource doesn't exist because it has an incorrect GVK, or if because it is a CRD that we don't know about, emit warning and skip resource from scan. The same for when policies are configured with a spec.rules GVK that the audit-scanner lacks permissions for, emit warning and skip resource from scan. Signed-off-by: Víctor Cuadrado Juan <[email protected]>
Signed-off-by: Víctor Cuadrado Juan <[email protected]>
Signed-off-by: Víctor Cuadrado Juan <[email protected]>
Needed, as we need a client when we do `fetcher.isNamespacedResource()`. Signed-off-by: Víctor Cuadrado Juan <[email protected]>
Signed-off-by: Víctor Cuadrado Juan <[email protected]>
Signed-off-by: Víctor Cuadrado Juan <[email protected]>
Add a test that checks that we don't error nor panic when trying to filter resources that are forbidden (because the client lacks permissions, normally because the ServiceAccount is insufficient). Signed-off-by: Víctor Cuadrado Juan <[email protected]>
Signed-off-by: Víctor Cuadrado Juan <[email protected]>
flavio
approved these changes
Jul 25, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice fixes, thanks!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fix #68
Test
Added unit tests.
Performed manual integration tests when developing:
Without the changes, we get a panic on
secrets
resource as they are forbidden.With changes applied:
Deploying the default policies, plus
safe-labels
policy targetting resources[pods, Pods, namespaces, secrets]
(note thatPods
is incorrect), we get the following WARN messages, for bothPod
(API resource not found) andsecrets
(API resource forbidden, unknown GVK or ServiceAccount lacks permissions):Additional Information
I recommend review per commit.
Tradeoff
Potential improvement
Refactor the filter packages after first MVP. Opened #74.