Detecting pods with DNS rule missing in VFP port and deleting the pods for mitigation#25
Open
princepereira wants to merge 3 commits into
Open
Conversation
princepereira
changed the title
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Runs the script from within a DaemonSet HPC pod with node-level context. The script identifies VFP ports that are missing DNS rules and maps those ports back to their corresponding pods. As an additional validation step, it executes a DNS query inside the pod using the crictl command.
If the DNS check still fails, the script deletes the affected pod using crictl. Since the deletion is initiated from the node itself, Kubernetes automatically recreates the pod on the same node through the DaemonSet. The newly created pod is then assigned a VFP port with the correct DNS rule installed.