-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
ci: upgrade the kubernetes versions for ci #12748
Conversation
@thotz I see we are pulling you image in code edit: because
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.
Great to see the CI is passing against K8s 1.28!
a886c43
to
c4ce2ff
Compare
@travisn I see |
Let's see if it passes after the latest push. I wouldn't think it's related to 1.28. But if we do find it's consistently failing, for now we can revert moving to 1.28 just fro that test suite. |
Is the pull failing for that image?? |
@thotz I have not checked that but |
@subhamkrai How about rebasing again to get a fresh test run? |
c4ce2ff
to
cb78cc4
Compare
done |
The object store is still failing on 1.28. How about reverting the object test to use 1.27 still so we can get this merged? We can track that with a separate issue. |
since, kubernetes v1.28.0 release upgrading the latest k8s version to v.1.28.0 excepth objectSuite tes. Signed-off-by: subhamkrai <srai@redhat.com>
cb78cc4
to
90d81e1
Compare
ci: upgrade the kubernetes versions for ci (backport #12748)
since, kubernetes v1.28.0 release upgrading the
latest k8s version to v.1.28.0 and minimum version to v1.23.17
Description of your changes:
Which issue is resolved by this Pull Request:
Resolves #
Checklist:
skip-ci
on the PR.