Daniel Messer

Hi @ricardozanini thanks for raising this. #1805 is about delegating the certification management to another stack but it would still have OLM trigger requesting and assigning the certs. It sounds...

This sounds like we would just support you shipping the webhook related manifests as part of the bundle and apply them as is, instead of making the webhooks part of...

Hi @vivekr-splunk https://github.com/operator-framework/operator-lifecycle-manager/blob/master/doc/design/subscription-config.md#volumemounts exists to augment a deployed operators with mounting an existing volume, but it doesn't seem that's quite what you are after. Can you comment on the use...

@thetechnick did you attempt to put in entries in the global pull secret scoped to a particular namespace in the respective registry, e.g. `quay.io/somenamespace/`

@thetechnick check out the current 4.9 docs for coverage: https://docs.openshift.com/container-platform/4.9/openshift_images/managing_images/using-image-pull-secrets.html#images-allow-pods-to-reference-images-from-secure-registries_using-image-pull-secrets

@thetechnick Yeah, makes a lot of sense. In this case just attach pull secrets to local service accounts in the namespace.

@thetechnick We discussed in the past what we could do with the current separation of controllers, the options weren't great (distribute the catalog `Secret` in all watch namespaces of the...

We've looked at this closer and there is probably a good middle ground we can land on in propagating the the secrets to the operator controller pods, since their definition...

Is this still an issue?

Thanks for filing this. This intentionally not being done today. The reason is the destructive nature of deleting CRDs - it will also delete all custom resource instances of the...