Add ip[6]tables support for Pod Identity feature #133
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:
#123
Description of changes:
Pod Identity introduced back at Dec 28, 2023
According to public documentation, Pod Identity uses the
hostNetwork
of the node and it uses port80
and port2703
on a link-local address on the node. This address is169.254.170.23
for IPv4 and[fd00:ec2::23]
for IPv6 clusters,Adding it into default iptables/ip6tables would be required.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.