add hostPorts to SecurityPolicyException for CAPI controllers with hostNetwork#198
Merged
pabateman merged 2 commits intoJun 24, 2026
Conversation
…stNetwork Signed-off-by: Artem Darmanyan <artem.darmanyan@flant.com>
Signed-off-by: Artem Darmanyan <artem.darmanyan@flant.com>
pabateman
approved these changes
Jun 24, 2026
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
2 participants
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.
When a CAPI infrastructure controller manager uses hostNetwork, container ports are accessible on the host network and are treated as hostPorts by the admission-policy-engine security policy check. The generated SecurityPolicyException only allowed hostNetwork but did not list the hostPorts, causing pod creation to fail with "hostPorts are not allowed, policy allows: []".