Web Console and CLI installation not the same
ALL-SPACE-Anas opened this issue · 1 comments
What happened:
OKD4.15 documentation describes two methods of installing KubeVirt Hyperconverged Cluster Operator, using webUI and CLI.
When installing from the webUI, you get the "kubevirt hyperconverged cluster operator" as expected. (I'm using channel 1.10.7 instead of stable because of #2954)
When following the command-line steps, you only get "community kubevirt hyperconverged".
Could I be missing something obvious here?
What you expected to happen:
Same results from WebUI and CLI installation methods.
How to reproduce it (as minimally and precisely as possible):
Install kubevirt hyperconverged cluster operator using the webUI, uninstall it and then install it again from the command-line.
Additional context:
NA
Environment:
- KubeVirt version (use
virtctl version): N/A - Kubernetes version (use
kubectl version): v1.28.2-3598+6e2789bbd58938-dirty - VM or VMI specifications: N/A
- Cloud provider or hardware configuration: Baremetal
- OS (e.g. from /etc/os-release): Fedora CoreOS 39.20240210.3.0
- Kernel (e.g.
uname -a): 6.7.4-200.fc39.x86_64 - Install tools: N/A
- Others: N/A
This is expected and it doesn't depend on the installation method. You are simply looking at different things:
community-kubevirt-hyperconverged is the package name, see:
while
KubeVirt HyperConverged Cluster Operator is the displayName, see: https://github.com/kubevirt/hyperconverged-cluster-operator/blob/84c79b00720e32c54f1a25baff18a1e03f095586/deploy/olm-catalog/community-kubevirt-hyperconverged/1.11.0/manifests/kubevirt-hyperconverged-operator.v1.11.0.clusterserviceversion.yaml#L188C3-L188C14