So when we did our testing over in https://issues.redhat.com/browse/AUTOSCALE-429 for OLMv1, we noticed two things: 

• OLMv1 doesn't seem to work for single-namespace installs 
• The VPA requires a watch namespace, which I'm not sure the GUI/Console will prompt users for in the new OLMv1 world

So before everything switches to 100% OLMv1, we probably need to figure out the right thing to do there. 

Everything works fine as long as you don't need a single-namespace install and/or you specify the required data to the VPA, e.g.: 

apiVersion: olm.operatorframework.io/v1
kind: ClusterExtension
metadata:
  name: vertical-pod-autoscaler-operator
spec:
  namespace: vertical-pod-autoscaler-system
  serviceAccount:
    name: vertical-pod-autoscaler-operator-installer
  source:
    sourceType: Catalog
    catalog:
      packageName: vertical-pod-autoscaler
      selector:
        matchLabels:
          olm.operatorframework.io/metadata.name: rh420-olmv1 
  config:
    configType: Inline
    inline: 
      watchNamespace: vertical-pod-autoscaler-system 

But we either are going to need to add our documentation or adjust our behavior to accommodate the new UX from Console for OLMv1. 

Done When

• We know what the Console UX is capable of for OLMv1 
• We know what next steps we need to take on our operators to make sure our UX is good/equivalent to today for OLMv1 
• We have cards written for those next steps