Skip to content
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

Add local built K8s images support in conformance test on Kind workflow #6248

Closed
luolanzone opened this issue Apr 22, 2024 · 1 comment
Closed
Assignees
Labels
priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@luolanzone
Copy link
Contributor

At the moment, we have a manual workflow to allow developers to run conformance test against different K8s versions.
https://github.com/antrea-io/antrea/blob/main/.github/workflows/conformance.yml
But it can only run those K8s versions which have been supported in kind repo, in most cases, we'd like to run Antrea with latest K8s versions which can help us to find the compatibility issues ASAP.

According to Kind README, users can build Kind Node images from K8s sources codes with following command, this allow us to build our own Node images and run the conformance test against the latest K8s version as earlier as possible. So it should be doable to add local built K8s Node image support to run conformance test workflow with a new parameter to specify a K8s commit or version tags.

kind build node-image
kind create cluster --image kindest/node:latest
@tnqn tnqn added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Apr 22, 2024
@luolanzone luolanzone added this to the Antrea v2.1 release milestone May 8, 2024
@luolanzone
Copy link
Contributor Author

Resolved by #6399

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Development

No branches or pull requests

3 participants