Alexander Wels
Alexander Wels
Hi, Would expect to be able to configure this on several levels or just one global level. There are basically 3 options 1. Global level. If this is set at...
We recently (yesterday) merged a PR that allows one to specify the file system overhead on a global and a per SC level. With a structured storage class map in...
Didn't we around that time split the CDI API into its own separate repo, which would stop the import of the CDI dependencies and that is probably why this is...
CDI is working on getting this sorted. libnbd is good to go according to fossa, and the cronexpr is dual licensed and includes apache 2.0. We are just dealing with...
So the hotplug code you are removing was added in https://github.com/kubevirt/kubevirt/pull/6079 and the PRs purpose was to allow a VM restart with hotplugged volumes that remain hotplugged after restart. I...
Okay so the attachment pod gets re-created, but because in the flow the attachment pod is created before the virt-launcher, we cannot take the selinux labels generated for the virt-launcher...
Okay I must be confused then, I thought we set the selinux labels in the securityContext in the pod spec, and I was thinking we were reading the value from...
I am honestly not entirely sure what the original purpose was. But if all the tests are passing, I would say it is not needed.
Well we would know all the hotplugged disks at the start so we would just create the one attachment pod will all the volumes associated with it.
Sure let me take a look