-
Notifications
You must be signed in to change notification settings - Fork 774
Remove Calico test suite from weekly integration tests #2559
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Hi @jdn5126 , Is it a maintenance burden to keep the CALICO test in weekly runs? If the suite has been healthy, don't see a harm in keeping the calico suite running in addition to the NP controller suite. I will defer the judgement to the maintainer(s) tough. |
The Calico tests are currently causing the weekly integration test runs to fail: https://github.com/aws/amazon-vpc-cni-k8s/actions/runs/6099567307/job/16552025168, and that was part of the motivation for this PR. The root cause seems to be from the helm upgrade, but that is still being investigated. The other motivation, and where I think the maintenance burden comes from, is that Calico leaves the cluster in a bad state after the tests finish. We do not have a way to uninstall Calico, so it always has to run last and requires the cluster to be deleted right after running. |
d6e1641
to
97d0e21
Compare
97d0e21
to
09db360
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
* 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]>
What type of PR is this?
cleanup
Which issue does this PR fix:
N/A
What does this PR do / Why do we need it:
This PR removes the Calico integration test suite from weekly integration test runs. Now that AWS VPC CNI supports Kubernetes Network Policy natively (via https://github.com/aws/aws-network-policy-agent), we do not need to test against Calico's Network Policy implementation as frequently. We will still test against Calico's Network Policy implementation before every release and treat any failure as a release gate.
Removing
RUN_CALICO_TEST
decreases the complexity ofrun-integration-tests
and decreases the overall runtime of our weekly integration test runner.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:
N/A
Automation added to e2e:
None
Will this PR introduce any new dependencies?:
No
Will this break upgrades or downgrades. Has updating a running cluster been tested?:
No, No
Does this change require updates to the CNI daemonset config files to work?:
No
Does this PR introduce any user-facing change?:
No
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.