This repository was archived by the owner on Jun 13, 2023. It is now read-only.
Tags: kubevirt/kubevirt-ansible
Tags
3 backports (#584) * moved cpu-node-labeller into initContainers (#582) Added second cpu-node-labeller into containers to sleep infinity and to hold pod running (cherry picked from commit 1627f15) * Comment out view test (#581) Something changed in kubevirt-0.13 that caused a regression test to fail. I think this needs to be addressed in kubevirt/kubevirt. Commenting out the test temporarily to unblock the gate. (cherry picked from commit 40e5183) * Expose CDI Upload Proxy service (#579) * add template for exposing cdi uploadproxy * provision and deprovision upload proxy route (cherry picked from commit 06a995c)
Update kubevirt013 (#556) (#576) * Update kubevirt-ansible to use kubevirt-0.13 Signed-off-by: Kedar Bidarkar <kbidarka@redhat.com> * Run `make deps-update` for kubevirt-0.13. As cdi used by kubevirt-0.13 is cdi-1.4.1+ and not cdi-1.5.0, removed the cdi entry from the glide.yaml file, so that we pull the cdi version from git commit from what the kubevirt-0.13 is using currently. Signed-off-by: Kedar Bidarkar <kbidarka@redhat.com> * Update the apiVersion to v1alpha3 Signed-off-by: Kedar Bidarkar <kbidarka@redhat.com> * update the flags to reflect container prefix Signed-off-by: Kedar Bidarkar <kbidarka@redhat.com> * Removed volumeName from disks for kubevirt-0.13.0 Signed-off-by: Kedar Bidarkar <kbidarka@redhat.com> * Fix secret and configmap tests for changes related to volumeName Signed-off-by: Kedar Bidarkar <kbidarka@redhat.com> * Fixed the kubevirt-cr and kubevirt-operator template files Dropped namespace creation in kubevirt-operator template and updated the apiversion. Signed-off-by: Kedar Bidarkar <kbidarka@redhat.com> (cherry picked from commit db35688)
distribute sr-iov configuration using initContainer (#539) In order to make network playbook operator friendly, we need to move node configuration to daemon sets. With this patch, node sr-iov DP configuration is stored in cluster-level config map and saved on a node using SR-IOV DP init container. The config map contains SR-IOV configuration per node (data key is name of the node) and 'fallback-config' in case specific node configuration is not provided. In order to reconfigure node's SR-IOV conf, config map must be updated and respective pod restarted.
PreviousNext