Tiger Kaovilai

> The name is only prefixed with there are two images with the same name, but different images. This does not fix the collision still. Is it just a notification...

I think a more obvious is to name something in all caps.. like OPERATOR_SDK_NAME_CONFLICT_originalname

You can't Ctrl+F your way to find "" as easily in the yaml.

Sounds like both "" and containerRef appending are notification mechanism.. but not a very consistent one.. since one adds to the name, and one removes the name.

@ryantking same usecase as previously stated in https://github.com/operator-framework/operator-sdk/issues/5000 which links to https://docs.openshift.com/container-platform/4.7/operators/operator_sdk/osdk-generating-csvs.html#olm-enabling-operator-for-restricted-network_osdk-generating-csvs that says to update > Update spec.relatedImages directly. They made no mention of RELATED_IMAGE_ in deployment. This was...

The specified relatedImage are potential images required in disconnected environments of supported [plugins](https://velero.io/plugins/) that user may choose to enable after.

Please add a note to the doc with info about prepending env with `RELATED_IMAGE_` I don't think that is clear in the doc as is. For our team, maybe but...

Resolving our team's relatedImages would definitely require more than dev team code changes since our release team have scripts which expects certain relatedImage names today. Per https://github.com/openshift/oadp-operator/pull/694 there are sideeffects...

What I am doing today (if this PR weren't merged) is to manually revert the removed relatedImages in relatedCSV so that I don't commit those into git. Not elegant.. not...

I'll try to make the meeting on Wednesday. Sounds like it maybe a good learning experience for me :)