fix(kubernetes): Add to nested resources on k8s graph inherit namespace #6912
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.
User description
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Description
I fixed the k8s build graph to inherit namespace for nested resources
Fixes # (issue)
New/Edited policies (Delete if not relevant)
Description
Include a description of what makes it a violation and any relevant external links.
Fix
How does someone fix the issue in code and/or in runtime?
Checklist:
Generated description
Below is a concise technical summary of the changes proposed in this PR:
Enhances the Kubernetes graph builder to inherit namespace for nested resources. Implements a new check to ensure resources are not in the default namespace. Adds corresponding test cases and resources for the new functionality. Updates existing test cases to reflect the changes in namespace handling.
Modified files (1)
Latest Contributors(2)
Modified files (1)
Latest Contributors(2)
Modified files (5)
Latest Contributors(2)