-
Notifications
You must be signed in to change notification settings - Fork 20
Conversation
cc @karmab |
ack |
We'll start with installing CNV 2.1 from brew for Dev and QE. When CNV 2.1 gets pushed out to prod, we'll change the script to consume the content from prod.
a3fbd70
to
3cf2d98
Compare
give it a try and hco-catalogsource-config deployment doesnt show up
|
Does using this script still require trusting insecure registries? And if so, do we already have something in install-scripts to do this? |
My PR #28 is pending and if an insecure registry is required it can be applied there... |
@rthallisey - when you address what @karmab raised, will you be able to test or will you need someone else to test it? |
oc get packagemanifest -n openshift-cnv
oc get csc -n openshift-marketplace
oc get operatorsource rh-osbs-operators -n openshift-marketplace
oc get catalogsource --all-namespaces
oc get pods -n openshift-marketplace |
|
also , output from oc get operatorsource rh-osbs-operators -n openshift-marketplace
|
@karmab can you access https://quay.io/application/rh-osbs-operators/kubevirt-hyperconverged ? Seems like your quay account doesn't have access |
My understanding is it does require the insecure registry. @nellyc can you comment? If it is needed for CNV-2.1 and none of the other pillars, I would think it should be classified as part of installing CNV-2.1, so we should look to the CNV team to add a script that will add it. But I could be wrong... maybe trusting an insecure registry is no longer needed (which would be quite nice) |
@rthallisey with the proper quay credentials, it worked! @johnbieren, it indeed requires access to an internal and insecure registry, which is something that is currently done through a post install script (launched prior to deploying cnv) @sreichar i think this can be merged |
Is the post install script in install-scripts? Or is it the one in Eduardo's PR he referenced? Or neither
|
AFAIK there is no internal/insecure registry configuration/machine-config right now into this repository |
We'll start with installing CNV 2.1 from brew for
Dev and QE. When CNV 2.1 gets pushed out to prod, we'll change
the script to consume the content from prod.