Antrea Jenkins Testbed Migration Plan

[XinShuYang]

Due to upcoming infrastructure changes, the Antrea Jenkins testbed will undergo a migration. Given the resource constraints, certain jobs will be permanently or temporarily disabled or modified. This plan will be carried out in two stages:

Stage 1 - Effective October 4th:

1. CAPV Jobs:
   • These jobs will be migrated from the CAPV testbed to the Kind testbed. This change is not permanent, and we will see the possibility of restoring CAPV or using another ClusterAPI solution when resources allow.
   • Impact to Developers: All tests triggered by the corresponding trigger phrases will now run on the Kind testbed, including /test-all,/test-e2e,/test-conformance,/test-networkpolicy,/test-all-features-conformance, /test-whole-conformance. cc @antoninbas @tnqn @luolanzone
2. IPv6 Jobs (Including IPv6-Only and Dual-Stack):
   • These jobs will be migrated to the Kind testbed, and all triggers will have the same effect as running the antrea-kind-ipv6 job.
   • Impact to Developers: All tests triggered by the corresponding trigger phrases will now run on the Kind testbed, including /test-ipv6-e2e,/test-ipv6-only-e2e,/test-ipv6-conformance,/test-ipv6-only-conformance, /test-ipv6-networkpolicy,/test-ipv6-only-networkpolicy, /test-ipv6-only-all, /test-ipv6-all. cc @hongliangl
3. IPAM Jobs:
   • These jobs will be migrated the Kind testbed, and all triggers will have the same effect as running antrea-kind-IPAM job.
   • Impact to Developers: All tests triggered by the corresponding trigger phrases will now run on the Kind testbed, including /test-flexible-ipam-e2e. cc @gran-vmv
4. Multicluster Job:
   • This job will be migrated to Kind testbed.
   • Impact to Developers: None, as this has already been part of the ongoing development plan. cc @hjiajing @luolanzone
5. EKS, AKS, and GKE Cloud Jobs:
   • These jobs will remain unaffected and will continue to be triggered periodically. Thanks @antoninbas and @edwardbadboy for the job migration support.
   • Impact to Developers: None.
6. Windows, External Node, and Multicast Jobs:
   • Due to the special infrastructure, these jobs will be migrated to a new testbed, which is managed by the new lab Jenkins. We will try our best to restore these jobs by October 4th, but due to resource and timing constraints, there is a risk of delays.
   • Impact to Developers: Jenkins CI jobs may be unavailable for some time after October 4th. cc @wenyingd cc @hongliangl @ceclinux @mengdie-song
7. Existing Kind-Related and Jenkins Jobs (e.g., Updater, Validator):
   • These jobs will remain unaffected. Thanks @KMAnju-2021 for the job migration.
   • Impact to Developers: None.
8. Remaining Jenkins Jobs:
   • All other Jenkins jobs will be disabled after October 4th. Some of them like rancher jobs will be restored in stage2, thanks @jainpulkit22 for the data migration.
   • Impact to Developers: You will no longer be able to trigger these jobs after October 4th.

Stage 2 - Timing TBD (After Stage 1 is completed and jobs are stable):

1. Restore CAPV-related jobs to run on the CAPV testbed.
2. Restore Rancher jobs.
3. Restore Jenkins backup jobs.
4. Consolidate Kind jobs with jobs that serve the same function.

A PR for updating job yaml will be opened for review during Stage 1. Please feel free to raise any questions or discussions regarding the plan in this issue, and we look forward to receiving feedback from the community. cc @tnqn @antoninbas @jianjuns @luolanzone @rajnkamr

[XinShuYang]

The Jenkins service at jenkins.antrea.io has been migrated to a new testbed. Currently, it is accessible only via HTTP. HTTPS will be enabled later.

[XinShuYang]

As planned, the stop-all job and Rancher jobs will be disabled on October 10th at 3 PM Pacific Time. cc @KMAnju-2021 @jainpulkit22

[XinShuYang]

Kind IPv6 jobs are available now, other IPv6 jobs have been disabled.

[XinShuYang]

The Windows testbed has been successfully migrated. However, due to recent resource constraints in our infrastructure, after discussion we have decided to shut it down before the 2.2 release to allocate more resources to other higher-priority projects. The latest patch fully verified by the Windows pipeline is aad06cd, and there should be no more Windows-related patches before the 2.2 release. Therefore, we can skip Windows Jenkins tests for the 2.2 release. cc @antoninbas @tnqn @luolanzone @wenyingd