CI Feature: Run K8s node-e2e tests in CRI-O CI

[kannon92]

We would like to be able to run main cri-o against latest master k8s to discover any regressions.

We want to be able to test different components with cri-o and k8s that upstream is not as interested in testing.

[sohankunkerkar]

We would like to be able to run main cri-o against latest master k8s to discover any regressions.

We are already using the master branch for CI.
We have two periodic jobs that run every day at 8:30 PM EST to build images with the latest Kubernetes codebase.

[kannon92]

How are we including the latest Kubernetes codebase?

[haircommander]

point of clarification: are we running node_e2e or e2e tests

[kannon92]

I want to run make test-e2e-node with the crio master, custom cri-o configs and k8s e2e_node test cases.

[sohankunkerkar]

point of clarification: are we running node_e2e or e2e tests

I guess we are running e2e tests

[sohankunkerkar]

I want to run make test-e2e-node with the crio master and custom ignition.

Are you thinking of adding a periodic job, or will it run on every PR? Our CI uses the PR content, not the master branch content, for running tests against changes.

[kannon92]

I was thinking a periodic is useful and a PR.

[kannon92]

Maybe we start with a periodic and we monitor that to catch potential issues with k8s and crio.

[sohankunkerkar]

See this PR. I think you need to do something similar, but you should add a separate workflow under step-registry/cri-o.

[github-actions]

A friendly reminder that this issue had no activity for 30 days.