Add ENABLE_V4_EGRESS env var to control IPv4 egress in IPv6 clusters #2577
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
achevuru
reviewed
Sep 21, 2023
jdn5126
force-pushed
the
enable_v4_egress
branch
from
2d42e24 to
716b302
Compare
achevuru
approved these changes
Sep 21, 2023
jdn5126
added a commit
that referenced
this pull request
Oct 20, 2023
* restore node update permission to master until image tag can be updated (#2513) * Merge branch 'release-1.14' (#2517) * network policies update to readme (#2478) * init draft of network policy desc * add security note * fixup * fixup * fix placeholder link * Update manifest for cni 1.14 (#2526) * Mimic VPC-RC limit struture (#2516) * limits api pkg (#2528) * Update kops tests for 1.28 and fix generate-cni-yaml script (#2536) * skip IPAMD events test (#2537) * chore: remove refs to deprecated io/ioutil (#2541) * Change default Node Agent ports for health and metrics (#2545) * remove self-managed node group from pod-eni test suite (#2547) * bump controller runtime to 0.16.1 (#2548) Co-authored-by: Joseph Chen <[email protected]> * update agent image (#2554) * fix(chart): Switch base64 encoded cniConfig.fileContents to the binaryData (#2552) * Update the use of privileged flag in aws-vpc-cni manifest (#2555) * increment default Calico version for helm compatibility (#2560) * update nginx image (#2561) * Only metrics (#2557) Prometheus metrics for capturing ENI IP usage and no available IP address errors Co-authored-by: Lindsay Hanks <[email protected]> * CHANGELOG, chart, and manifest updates for VPC CNI v1.15.0 release (#2563) * remove calico test suite from weekly integration tests (#2559) * remove addon-tests integration suite as it is no longer needed (#2564) * Only metrics (#2569) * rename warm pool metrics --------- Co-authored-by: Lindsay Hanks <[email protected]> * Fix unused version variable (#2566) * Update example table 'Pod per Prefixes' value (#2573) * Bandwidth plugin with NP is currently unsupported (#2572) * Bandwidth plugin with NP * Messaging review * pass CNINode scheme to client only (#2570) * reduce api calls (#2575) * Add region flag to describe-addon command (#2576) * add ENABLE_V4_EGRESS (#2577) * Add test registry parameter for ipv6 and CNI full tests (#2585) * update golang image (#2586) * increase time for service readiness (#2587) * do not patch CNINode for custom networking unless podENI is enabled (#2591) * Remove self-managed node group from custom-networking suite (#2590) * remove self-managed node group from custom-networking suite * Select CNI manifest based on regions (#2593) * Update metrics helper image url based on region (#2604) * dependabot updates (#2605) * Graceful termination for service connectivity tests (#2611) * update CHANGELOG, charts, and manifests in master following v1.15.1 release (#2614) * go module updates and golang builder image update (#2615) * update Golang to 1.21.3 (#2616) * Stricter dependency/security review (#2617) * Stricter dependency/security review Signed-off-by: Davanum Srinivas <[email protected]> * move common things to a separate file Signed-off-by: Davanum Srinivas <[email protected]> --------- Signed-off-by: Davanum Srinivas <[email protected]> * update actions for go 1.21 and fix deps action warnings (#2618) --------- Signed-off-by: Davanum Srinivas <[email protected]> Co-authored-by: Jay Deokar <[email protected]> Co-authored-by: Geoffrey Cline <[email protected]> Co-authored-by: Joseph Chen <[email protected]> Co-authored-by: guangwu <[email protected]> Co-authored-by: Joseph Chen <[email protected]> Co-authored-by: Valentin Zayash <[email protected]> Co-authored-by: lnhanks <[email protected]> Co-authored-by: Lindsay Hanks <[email protected]> Co-authored-by: 김은빈 <[email protected]> Co-authored-by: Jayanth Varavani <[email protected]> Co-authored-by: Davanum Srinivas <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What type of PR is this?
feature
Which issue does this PR fix:
aws/aws-network-policy-agent#55
What does this PR do / Why do we need it:
This PR adds a new environment variable,
ENABLE_V4_EGRESS, which controls whether theegress-cnichained plugin is enabled for IPv6 clusters. The value is enabled by default, preserving the existing IPv6 default. When disabled, an IPv4 interface will not be created in IPv6 pods, blocking those pods from reaching IPv4 endpoints.The primary motivation for this PR is to address aws/aws-network-policy-agent#55, where the concern is network policies in IPv6 clusters not applying to IPv4 traffic.
If an issue # is not available please add repro steps and logs from IPAMD/CNI showing the issue:
N/A
Testing done on this change:
Manually verified that chained plugin is enabled or disabled based on env var.
Automation added to e2e:
N/A
Will this PR introduce any new dependencies?:
No
Will this break upgrades or downgrades. Has updating a running cluster been tested?:
No, Yes
Does this change require updates to the CNI daemonset config files to work?:
No
Does this PR introduce any user-facing change?:
Yes
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.