Description of problem: When deploying KubeVirt using APB it deploys CDI into golden-images namespace. Based on https://access.redhat.com/articles/3500741 article CDI should land in kube-system namespace. Version-Release number of selected component (if applicable): kubevirt-apb-1.2-5 How reproducible: Always Steps to Reproduce: 1. Deploy KubeVirt using APB 2. Wait for pods to roll out 3. Observe what is namespace of CDI pod Actual results: it is running in golden-images namespace Expected results: It should run in kube-system namespace Additional info:
Lukas should this be for both upstream and downstream?
@Ryan since that document [1] is related to d/s, I am good with this change being done on d/s only. Here [2] is u/s guide, which says default is good to go for testing that out ... I believe the best practice is add parameter for APB, so in that way it is configurable. [1] https://access.redhat.com/articles/3500741 [2] https://github.com/kubevirt/containerized-data-importer/#deploying-cdi
@Ryan, whats the status here? should the bug move to post/modified/qe? can we target it to 1.3?
The latest kubevirt-ansible build has the fix: https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=19079025 But, I'm still not able to build the apb because of https://projects.engineering.redhat.com/browse/FACTORY-3482.
Thanks Ryan, we will wait for it please move to ON_QA & fill in the 'fixed in version' once the build is ready
brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/cnv-tech-preview/kubevirt-apb:v1.3.0-5
It is fixed in kubevirt-apb-v3.11-4
I think this is targeted for 1.3