Make advertising port 80 optional #107
Merged
Conversation
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
kmala
reviewed
Nov 4, 2025
eks-pod-identity-agent only bind on 169.254.170.23 and fd00:ec2::23 for port 80.
By configuring the portmap cni plugin to exclude those 2 addresses
```
{
"type": "portmap",
"capabilities": {"portMappings": true},
"snat": true,
"conditionsV4": ['!', '-d', '169.254.170.23'],
"conditionsV6": ['!', '-d', 'fd00:ec2::23']
}
```
we can have a pod using `hostPort: 80` (let's say ingress-nginx) and
eks-pod-identity-agent running on the same node, we just need `advertiseProxyPort: false`.
champtar
force-pushed
the
helm-advertisePort80
branch
from
b7dcce4 to
598b058
Compare
kmala
approved these changes
Nov 5, 2025
Contributor
Author
|
Thanks @kmala |
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.
Issue #, if available:
#10
Description of changes:
eks-pod-identity-agent only bind on 169.254.170.23 and fd00:ec2::23 for port 80. By configuring the portmap cni plugin to exclude those 2 addresses
we can have a pod using
hostPort: 80(let's say ingress-nginx) and eks-pod-identity-agent running on the same node, we just needadvertisePort80: false.see also aws/amazon-vpc-cni-k8s#3497
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.