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

Upgrade CRI-O to 1.18.3 #8388

Closed
afbjorklund opened this issue Jun 5, 2020 · 9 comments · Fixed by #8404 or #8923
Closed

Upgrade CRI-O to 1.18.3 #8388

afbjorklund opened this issue Jun 5, 2020 · 9 comments · Fixed by #8404 or #8923
Assignees
Labels
area/guest-vm General configuration issues with the minikube guest VM co/runtime/crio CRIO related issues kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone

Comments

@afbjorklund
Copy link
Collaborator

afbjorklund commented Jun 5, 2020

For Kubernetes 1.19 etc, move to crio 1.18.1 and podman 1.9.3

EDIT: Most likely, this also needs a newer version of conmon

@afbjorklund afbjorklund added the co/runtime/crio CRIO related issues label Jun 5, 2020
@afbjorklund afbjorklund changed the title Upgrade CRI-O Upgrade CRI-O to 1.18.1 Jun 5, 2020
@afbjorklund afbjorklund self-assigned this Jun 5, 2020
@afbjorklund afbjorklund added area/guest-vm General configuration issues with the minikube guest VM kind/feature Categorizes issue or PR as related to a new feature. labels Jun 5, 2020
@afbjorklund afbjorklund added this to the v1.12.0-candidate milestone Jun 5, 2020
@afbjorklund afbjorklund added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Jun 8, 2020
@afbjorklund
Copy link
Collaborator Author

afbjorklund commented Jul 6, 2020

Reverted, because of the OS downgrade (and thus the Go version)

@afbjorklund afbjorklund reopened this Jul 6, 2020
@medyagh medyagh modified the milestones: v1.12.0, v1.13.0-candidate Jul 8, 2020
@afbjorklund
Copy link
Collaborator Author

afbjorklund commented Jul 18, 2020

Blocked on #7904 and still missing upstream: cri-o/cri-o#3844

@afbjorklund
Copy link
Collaborator Author

afbjorklund commented Aug 5, 2020

Stealth upgraded for Ubuntu, but still pending for Buildroot

61583d6

@afbjorklund afbjorklund changed the title Upgrade CRI-O to 1.18.1 Upgrade CRI-O to 1.18.3 Aug 5, 2020
@medyagh
Copy link
Member

medyagh commented Sep 16, 2020

we could do this after buildroot upgrade

@renich
Copy link

renich commented Sep 16, 2020

Can we just jump directly to cri-o v1.19.0?

@afbjorklund
Copy link
Collaborator Author

Theoretically, but they bumped to go 1.15

@afbjorklund
Copy link
Collaborator Author

Most likely we will end up using CRI-O 1.19 with Kubernetes 1.20 or something, that is how it usually works out...

@medyagh medyagh modified the milestones: v1.14.0, v1.15.0-candidate Oct 12, 2020
@priyawadhwa
Copy link

If we're skipping 1.18.3, can this issue be closed?

@afbjorklund
Copy link
Collaborator Author

If we're skipping 1.18.3, can this issue be closed?

We're not skipping 1.8.3 as far as I know at least.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/guest-vm General configuration issues with the minikube guest VM co/runtime/crio CRIO related issues kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
4 participants