Ben Parees

I'd expect to see some discussion of the subscription.spec.config.nodeSelector and subscription.spec.nodeAffinity([new 4.12](https://github.com/openshift/operator-framework-olm/commit/eea791fc0921379a54b1442e8d67f5bed614a72a)) and how that can also set nodeselector/affinity values on the operator deployment.

> I feel like it would probably be closer to the OLM functionality than OperatorSDK. I can absolutely cross-link the docs for that from this guide, though. yup, my original...

how is that different from running it, letting it setup the storage, and then killing it, and then running it again later? @mnagy fyi.

i'd vote for doing this w/ an env variable then. -e SETUP_ONLY=true

@bmcelvee can help you w/ the docs,or you can make a PR directly: the 3.11 docs are here (master branch for now, though master branch may become 4.x soon) https://github.com/openshift/openshift-docs/blob/master/using_images/s2i_images/python.adoc...

> @bparees Does it make sense to maintain the documentation in two places? We update it fairly often and send a PR every time we do so does not scale....

> If I understand it correctly, users can import any container image they want but OpenShift also offers some defaults and those default images are documented in the OpenShift documentation....

> What I'm wondering is when this import happens -- is it once for each major OCP version or regularly for minor updates? I.e. if we release a new version...

> Does it make sense? yeah it makes sense, that sort of scenario is what i was hedging against with "most likely". Certainly new behaviors might be introduced and effectively...

@mnagy +1, this sounds like an excellent idea.