cri-o: keep track of the new cri-o release

[Pennyzct]

Description of problem

Lately, in PR #2458, we temporarily updated cri-o version to commit ID of the fix.
All following significant fixes are not included in the latest stable tag version v1.17.0.

• PR [1.17] bump c/image to 5.2.1 cri-o/cri-o#3239 is critical for running cri-o v1.17.x on AArch64, and specific reason is elaborated here cri-o 1.17.0 breaks ARM clusters cri-o/cri-o#3233.

• PR cri-o: fix netns mount point leaking from cri-o tests#2305 needs to include commit Skip invalid hooks directories by default cri-o/cri-o#3203 in cri-o v1.17.x.

Let's keep track of the new stable cri-o release . ;)

[Pennyzct]

Hi guys

cri-o has new stable release v1.17.2, and it included the changes in cri-o/cri-o#3239.

But for another change cri-o/cri-o#3203 we wanted to include, I just found that, it will not be included in any v1.17.x release, it has been merged into master and may plan to include it in the future v1.18.x.
I could use a temporary workaround to fix it until the new v1.18.x age is coming.
but Wdyt, @devimc @amshinde @chavafg , we keep waiting or upgrade it to v1.17.2?

[fidencio]

v1.17.3 is out already. And it does include some fixes needed when using shimv2, such as: cri-o/cri-o#3530

If bumping, may be worth to bump to v1.17.3

[devimc]

@Pennyzct @fidencio what about the 1.18 release candidate? may worth to try it out and be ready for the stable release?

https://github.com/cri-o/cri-o/releases/tag/v1.18.0-rc1

[fidencio]

@devimc, I do think so.
@haircommander, I'd guess you're totally in favour on getting the tests in the latest cri-o, even if that means a release candidate, right? :-)

[haircommander]

definitely in favor!

[amshinde]

I am fine with moving to 1.18.0-rc1.
@chavafg We should move to testing with kubernetes 1.18 as well in our CI.

[chavafg]

Yeah, we should move the k8s version at the same time. And also the Sonobuoy version to 0.18

[amshinde]

@chavafg cri-o 1.18 has landed. We should move to this version:
https://cri-o.github.io/cri-o/v1.18.0

cc @jodh-intel Copying you in for reference to the release notes from cri-o. I think the split of the commits in the release notes into bugs, features and documentation is pretty neat.

[jodh-intel]

Thanks @amshinde - that triggered me to remember to raise an issue on "conventional commits": kata-containers/kata-containers#195.