| kata-irc-bot | <fidencio> And this is the current action running: https://github.com/kata-containers/kata-containers/actions/runs/1031992150 | 06:59 |
|---|---|---|
| kata-irc-bot | <fidencio> ```+ kubectl apply -f ./tools/packaging/kata-deploy//examples/nginx-deployment-qemu.yaml NAMESPACE NAME STATUS ROLES AGE VERSION LABELS node/k8s-agentpool-15410489-0 Ready agent 83s v1.20.5 | 08:49 |
| kata-irc-bot | agentpool=agentpool,beta.kubernetes.io/arch=amd64,beta.kubernetes.io/instance-type=Standard_D4s_v3,beta.kubernetes.io/os=linux,failure-domain.beta.kubernetes.io/region=westus2,failure-domain.beta.kubernetes.io/zone=0,kubernetes.azure.com/cluster=kata-deploy-594ff3a5bd,kubernetes.azure.com/role=agent,kubernetes.io/arch=amd64,kubernetes.io/hostname=k8s-agentpool-15410489-0,kubernetes.io/os=linux,kubernetes.io/role=agent,node-role.kubernetes.io/agent | 08:49 |
| kata-irc-bot | =,node.kubernetes.io/instance-type=Standard_D4s_v3,storageprofile=managed,storagetier=Premium_LRS,topology.kubernetes.io/region=westus2,topology.kubernetes.io/zone=0 node/k8s-master-15410489-0 Ready master 83s v1.20.5 | 08:49 |
| kata-irc-bot | beta.kubernetes.io/arch=amd64,beta.kubernetes.io/instance-type=Standard_D2_v2,beta.kubernetes.io/os=linux,failure-domain.beta.kubernetes.io/region=westus2,failure-domain.beta.kubernetes.io/zone=0,kubernetes.azure.com/cluster=kata-deploy-594ff3a5bd,kubernetes.azure.com/role=master,kubernetes.io/arch=amd64,kubernetes.io/hostname=k8s-master-15410489-0,kubernetes.io/os=linux,kubernetes.io/role=master,node-role.kubernetes.io/master=,node.kubernetes.io/ | 08:49 |
| kata-irc-bot | exclude-disruption=true,node.kubernetes.io/exclude-from-external-load-balancers=true,node.kubernetes.io/instance-type=Standard_D2_v2,topology.kubernetes.io/region=westus2,topology.kubernetes.io/zone=0 verify connectivity with a pod using Kata deployment.apps/nginx-deployment-qemu created + sleep 3 + kubectl wait --timeout=5m --for=condition=Available deployment/nginx-deployment-qemu error: timed out waiting for the condition on | 08:49 |
| kata-irc-bot | deployments/nginx-deployment-qemu + destroy_aks + set +x``` | 08:49 |
| kata-irc-bot | <fidencio> @jose.carlos.venegas.m, @eric.ernst, in the AKS environment where we test kata-containers, do we know the CRI runtime we use and its version? As in, CRI-O or containerd? Which version of those? | 19:41 |
| kata-irc-bot | <jose.carlos.venegas.m> I dont know, whatever th AKS installs | 19:42 |
| kata-irc-bot | <jose.carlos.venegas.m> I think we dont control that version | 19:42 |
| kata-irc-bot | <jose.carlos.venegas.m> you still got problems? | 19:42 |
| kata-irc-bot | <fidencio> I am starting to debug this now (don't ask, really bad day with -ETOOMANY meetings) ... and there's one thing that crossed my mind as a possible root cause of the issue we're facing | 19:43 |
| kata-irc-bot | <fidencio> https://github.com/kata-containers/kata-containers/pull/2040#issuecomment-871633740 | 19:47 |
| kata-irc-bot | <eric.adams> If anyone else is suffering with proxy issues and has an extra NUC/server with 2 ethernet ports along with an extra switch I can give them some instructions on how to build a proxy router. At least I know how to do it inside Intel using redsocks and Linux. I use a proxy router for upstream traffic into my cluster the same way others use load balancers. As @eric.ernst probably remembers (since we sat right next to each other) I had it | 22:22 |
| kata-irc-bot | on my desk and it saved me a ton of time not having to chase down misconfigured proxies. | 22:22 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!