-
Notifications
You must be signed in to change notification settings - Fork 24
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
fixes: update k8s repo location, use latest releases in e2e tests. #279
Conversation
You were on it, too... I think this patch wins #280 by fixing the issue on deb packages, too. But if possible, I'd still like the e2e framework to automatically pick the latest k8s version unless user forces one. If you prefer having the version number in the playbook more than run(_tests).sh env var, let's have it there. (Maybe move to |
31b4b96
to
a6b95e1
Compare
@askervin I added overridable autodetection of latest K8s release. It successfully installed 1.29.2 in my balloons tests. |
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.
Great, thanks @klihub!
1834244
to
707db70
Compare
707db70
to
ae9c560
Compare
@askervin Updated to autodetect both latest K8s and runtime version. PTAL.
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, works great (running groupBy tests on Fedora now)
Switch provisioning of both fedora and ubuntu-based e2e test VMs to the pkgs.k8s.io repositories. Also try autodetecting and using the latest available K8s, containerd and CRI-O releases/versions, unless this is overridden by the user. Signed-off-by: Krisztian Litkey <krisztian.litkey@intel.com>
ae9c560
to
b27c140
Compare
Update e2e test VM provisioning to use the new
pkgs.k8s.io
repositories. Also autodetect and use the latest Kubernetes, containerd and CRI-O versions, unless this is overridden by the user.