Closed luolanzone closed 11 months ago
And one thing I noticed that the existing testbed is v1.22 which is an old K8s version, we'd better to upgrade to a newer one.
@tnqn @XinShuYang any suggestion regarding to the testbed's K8s version? I feel it's better to be v1.25 or higher. The reason is kubectl debug
requires EphemeralContainers
feature gate which is default to true since v1.25. I feel this can help us to debug easier.
For Kubernetes v1.25 or higher, it is necessary to add an additional node with Docker support to the cluster for building the Antrea image. This is because Docker is no longer supported on the cluster nodes. cc @luolanzone @hjiajing
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment, or this will be closed in 90 days
Since ipv6 jobs have been updated, we can close this issue and use #5649 to track long-term testbed upgrade.
Describe what you are trying to solve Antrea relys on CI heavily to continuously verify code changes in PRs. But we often encounter different testbed issues for PR changes verification, especially for dual-stack and ipv6-only testbed. For now, we only have one dual-stack and one ipv6-only test bed. It's hard to do troubleshooting, and may have impacts for any running Jenkins job. If we make the testbed offline, it will block the CI.
Describe the solution you have in mind We'd better to prepare two new testbeds for dual-stack and ipv6-only which can be helpful especially when there are lots of PRs waiting for verification before a new release.