-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't have interface with glusterfs stroage generated after provisioning kubevirt-apb via web console #57
Comments
@qwang1 This comment is not related to your issue, it is just a note about kubevirt version: the latest released is v0.5.0, and pre-released is v0.5.1-alpha.2 ... unfortunately you can not deploy these from WebConsole (because hardcoded enum in apb), but you can create serviceinstance manually with what ever params you like, for example for latest kubevirt use: # kubevirt-apb.yml
---
apiVersion: servicecatalog.k8s.io/v1beta1
kind: ServiceInstance
metadata:
name: kubevirt
namespace: kube-system
spec:
clusterServiceClassExternalName: "dh-virtualization"
clusterServicePlanExternalName: gluster
parameters:
admin_user: "test_admin"
admin_password: "123456"
version: "0.5.1-alpha.2" oc create -f kubevirt-apb.yml |
@lukas-bednar Yes, the version on apb.yml file should be updated. However, I saw a new file download-templates.sh was added and get the latest version with kubevirt release, I have no idea where this script is used. |
ansibleplaybookbundle/apb-base#31 fixed the issue. I just updated the dockerhub image docker.io/ansibleplaybookbundle/kubevirt-apb:latest to make sure it has the fix. Make sure you're using newest image. Reopen if the issue persists. |
…-kubevirt-on-openshift Added playbook which install KubeVirt on existing OpenShift cluster
Hi there,
So far the latest kubevirt-apb version is v0.4.1-alpha.2. I tried to provision it with glusterfs storage checked on OCP v3.10.0-0.47.0 + OpenStack. There is no kubvirt storageclass generated. Seems it didn't run storage part. If I use ansible-playbook to deploy kubevirt.yml, this problem won't happen http://pastebin.test.redhat.com/598551.
@rthallisey Could you take a look at it? Thanks.
The text was updated successfully, but these errors were encountered: