Conversation
JoseVillalta
approved these changes
Mar 6, 2026
aaithal
approved these changes
Mar 6, 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
5 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.
Summary
Problem: createBridgePluginConfig() (for awsvpc tasks) only configured IPv4 on the fargate-bridge. Awsvpc tasks had no IPv6 address on the bridge, so they couldn't reach daemon tasks via IPv6.
Fix: Add IPV6Subnet: ECSSubNetIPv6 ("fd00:ec2::172:0/112") so IPAM allocates IPv6 addresses to awsvpc tasks on the bridge.
Before: Awsvpc task eth0 has only 169.254.172.3/22
After: Awsvpc task eth0 has 169.254.172.3/22 AND fd00:ec2::172:3/112
Test updated: cniconf_linux_test.go - Added IPV6Subnet to expected config in TestCreateBridgeConfig.
Description for the changelog
Add IPv6 subnet to IPAM config.
Additional Information
Does this PR include breaking model changes? If so, Have you added transformation functions?
Does this PR include the addition of new environment variables in the README?
Licensing
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.