Options:

• Consider changing the wording of the introduction sentences that `recommends` to use the upstream puller.
  Let me know if I should write a comment or note about using the community feature under the development.
• Close this issue if everything is ok after all.
• Put the info about the better "names" of CRW attributes.

• Make sure those are updated:

// Image puller
:image-puller-cr-name: KubernetesImagePuller
:image-puller-deployment-name: kubernetes-image-puller
:image-puller-image-tag: {prod-ver}
:image-puller-image-name: {rhio-url}/codeready-workspaces/imagepuller-rhel8:{prod-ver}
:image-puller-operator-name: Kubernetes Image Puller Operator
:image-puller-name: Kubernetes Image Puller
:image-puller-name-short: Image Puller
:image-puller: {rhio-url}/codeready-workspaces/imagepuller-rhel8:{prod-ver}
:image-puller-tag: {prod-ver}

Check their role in the AG.

Context:
https://access.redhat.com/documentation/en-us/red_hat_codeready_workspaces/2.5/html-single/administration_guide/index#deploying-image-puller-using-operator_crw