Monday, 2020-03-09

*** igordc has joined #kata-dev03:19
*** igordc has quit IRC06:31
*** jodh has joined #kata-dev08:11
*** sgarzare has joined #kata-dev08:22
*** davidgiluk has joined #kata-dev09:02
*** gwhaley has joined #kata-dev09:04
*** pcaruana has joined #kata-dev10:10
*** sgarzare has quit IRC10:23
*** sgarzare has joined #kata-dev10:33
*** gwhaley has quit IRC12:00
*** devimc has joined #kata-dev12:55
*** canyounot has joined #kata-dev13:14
*** fuentess has joined #kata-dev13:15
*** gwhaley has joined #kata-dev13:22
*** lpetrut has joined #kata-dev14:49
*** lpetrut has quit IRC16:05
*** sgarzare has quit IRC17:54
*** jodh has quit IRC18:04
*** gwhaley has quit IRC18:06
*** pcaruana has quit IRC19:23
*** davidgiluk has quit IRC20:03
*** canyounot has quit IRC20:45
*** canyounot has joined #kata-dev20:46
*** canyounot has quit IRC21:22
*** devimc has quit IRC21:51
kata-irc-bot<fidencio> @julio.montes, @gabriela.cervantes.te, @archana.m.shinde, I'm facing one test failure when running k8s e2e tests against my cluster that may be related to a shimv2 comment I've seen in your github22:42
kata-irc-bot<fidencio> What's the state of the shimv2? Was it merged? When?22:42
kata-irc-bot<archana.m.shinde> @fie22:46
kata-irc-bot<archana.m.shinde> We need to fix the crio restart issue mentioned there22:47
kata-irc-bot<archana.m.shinde> I was planning to take a look at that, but it may be another week or two before I get to it22:47
kata-irc-bot<archana.m.shinde> We have done our e2e testing with kata shimv1 if I may call it so22:48
kata-irc-bot<archana.m.shinde> We do need to add e2e testing with shimv222:49
kata-irc-bot<archana.m.shinde> what's the failure that you are seeing?22:49
kata-irc-bot<fidencio> @archana.m.shinde, the failure is in the "[sig-cli] Kubectl client Simple pod should support port-forward" testcase22:50
kata-irc-bot<fidencio> IIUC, pod port-forward is depends on shimv2, doesn't it?22:51
kata-irc-bot<fidencio> Or, more specifically, may be related to https://github.com/kata-containers/runtime/issues/69722:51
kata-irc-bot<archana.m.shinde> ahh port-forwarding22:52
kata-irc-bot<archana.m.shinde> that does not really depend on shimv2, but yes, it would be easier to resolve in shimv222:53
kata-irc-bot<archana.m.shinde> port-forwarding in CRI implementations assume namespaces22:53
kata-irc-bot<archana.m.shinde> this could potentially be fixed by extending the shimv2 interface and having an Portforward Interface in shimv2 api22:54
kata-irc-bot<archana.m.shinde> @fidencio we have had discussions in the past about it iirc, but since Portforwars is mostly a debug feature, it hasnt got too much attention lately22:56
kata-irc-bot<fidencio> Right, I will have to check with Mrunal whether it's something we actually should care or not22:56
kata-irc-bot<fidencio> If not, better. If we should, well, then we'll work on that :slightly_smiling_face:22:57
*** fuentess has quit IRC22:57
kata-irc-bot<fidencio> @archana.m.shinde, thanks for the explanation, appreciated!22:59
kata-irc-bot<archana.m.shinde> sure @fidencio22:59
kata-irc-bot<archana.m.shinde> let me know if this is something that needs to be looked at23:00

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!