-
Notifications
You must be signed in to change notification settings - Fork 374
Conversation
Move to k8s 1.10 Fixes: kata-containers#277 Signed-off-by: Jose Carlos Venegas Munoz <jose.carlos.venegas.munoz@intel.com>
I was talking with the CRI-O guys and there will be compatibility issues between Openshift and Kubernetes, because latest Openshift v3.9 should use CRI-O 1.9 and k8s 1.10 should use CRI-O 1.10. There isnt still an Openshift 3.10 out, neither an alpha release. So I think we will need to have a way to test crio 1.9 with openshift v3.9.0 and crio 1.10 with k8s 1.10 |
I was thinking Fedora to run Openshift tests and ubuntu to run k8s, what do you think @sboeuf @egernst @jcvenegas ? |
@chavafg this makes a lot of sense to me - a natural division. |
Update our supported openshift version from v3.7.1 to v3.9.0 Signed-off-by: Salvador Fuentes <salvador.fuentes@intel.com>
1 similar comment
Using k8s 1.10.0 |
The issue is already reported on kubeadm: kubernetes/kubeadm#748 I think the only option here is to add a workaround in the tests to delete the pods after running |
Hi @chavafg - sounds reasonable to me. |
Since we want to test under kubernetes 1.10 and we also want to supoort latest version of Openshift, which is v3.9.0, we need to test with with different versions of CRI-O. K8s 1.10 should use cri-o 1.10, while openshift v3.9.0 should use v1.9 Depends-on: github.com/kata-containers/tests#277 Signed-off-by: Salvador Fuentes <salvador.fuentes@intel.com>
Codecov Report
@@ Coverage Diff @@
## master #278 +/- ##
==========================================
- Coverage 64.53% 64.38% -0.15%
==========================================
Files 86 86
Lines 8397 8432 +35
==========================================
+ Hits 5419 5429 +10
- Misses 2404 2428 +24
- Partials 574 575 +1
Continue to review full report at Codecov.
|
@chavafg Yes, that sounds fine. Lets create an issue for it so we dont forget. |
opened kata-containers/tests#296 to delete the workaround when the issue gets properly fixed. |
This is ready to be merged, but please when merge this, please also merge this one in tests repository: kata-containers/tests#277 |
As we need CRI-O 1.9 to run tests on openshift v3.9.0 (latest) and CRI-O 1.10 to run Kubernetes 1.10, we need to make a division in our CI, so that we can test both scenarios without adding more execution time to the CI jobs. Because of this, we will execute CRI-O 1.9 - openshift v3.9.0 tests under Fedora and CRI-O 1.10 - Kubernetes 1.10 tests under ubuntu. Fixes: clearcontainers#276. Depends-on: github.com/kata-containers/runtime#278 Signed-off-by: Salvador Fuentes <salvador.fuentes@intel.com>
Using random char generation at early boot may slow the process due to low entropy. Also from kernel 4.14.36 rand call hangs due to low-entropy. Lets remove dependency on rand at early sandbox creation. Fixes: kata-containers#278 Signed-off-by: Jose Carlos Venegas Munoz <jose.carlos.venegas.munoz@intel.com>
Move to k8s 1.10
Fixes: #277
Signed-off-by: Jose Carlos Venegas Munoz jose.carlos.venegas.munoz@intel.com