#kubevirt

rmohr: hey there got a minute? I encountered broken manifests, the syntax is wrong and kubernetes is not happy with it :). Do we have them broken?

pkotas: don't think so in general. I am using them right now and don't see any issues

pkotas: what is the error you see?

rmohr: haproxy.yaml.in:26 wrong indentation

this repeats in several files and kubernetes is complaing about it

pkotas: that looks like you try to deploy the template and not the manifest itself

pkotas: you need to deploy manifest/*.yaml

rmohr: in fact i am deploying the yaml not the in :).

i used it for you to find it quickly

pkotas: did you already check the usual things? Unintentionally change the manifest, not on latest master, ...

I pulled master right now

but hold i will send link to guthub :)

rmohr: https://github.com/kubevirt/kubevirt/blob/da9b3...

its there

pkotas: looks like on my machine

pkotas: can you share the generated manifest from that service?

I have it fixed :) on my machine, but I can go back. The difference could be, i am trying to deploy on minikube and it has different setting for linting

this is the generated

rmohr: besides the whitespace, its the same

Heya

Weekly starts in ~7 please take your time to add your item to the agenda:

Hi folks, this is a long-shot I know. Over in #openstack-kolla - we're seeing a fairly long-standing issue with libvirt running in a kolla container. The bug is: https://bugs.launchpad.net/kolla/+bug/1733806 - was wondering if you guys have seen anything similar? It looks and feels like an upstream qemu change. Looks like the TLS setup isn't correct, no cert file - but this is about as far as I got.

Hi rwellum, we use unix sockets to communicate with libvirt so KubeVirt's approach sidesteps that issue

Ah - makes sense - ty.