Fix ebpf maps/progs cleanup test #376
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
jaydeokar
approved these changes
Mar 12, 2025
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.
Issue #, if available:
With recent changes in NP, every pod will have maps/progs created even if policies are not applied to it. Once we run cyclonus tests and clean up the pods and policies, we run a pod which runs cleanup script to check if there are any leaked maps or progs on the node. As we are creating a new pod for this, there will be maps/progs created for this pod.
Description of changes:
Exclude maps/progs with cleanup pod name while checking for leaked maps/progs. core dns pods will also have default probes attached as it is a deployment. Excluding those too
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.