Improve Ansible User Guide documentation for Building/Running the Operator

[ryandgoulding]

Feature Request

Is your feature request related to a problem? Please describe.
The existing documentation may cause confusion for new users with respect to building and running the example memcached operator. Namely, "quay.io/example/v0.0.1" is used in several places without much explanation. Extracting an environment variable to represent this value could improve usability; specifically by implying that a user should replace "example" with his or her quay.io username. Additionally, the user guide is focused on the quay.io docker registry, which is perfectly acceptable. However, when I ran through the example, I did not realize that the repository must be made public in order for K8S to successfully pull the image. This might be personal naivete, but I believe the documentation could benefit from explicitly mentioning that the repository should be made public.

Describe the solution you'd like
One solution might involve the following steps:

1. Have the documentation extract an environment variable to represent the Docker Image, so that it is consistent throughout and less prone to copy/paste error.
2. Mention that the quay.io docker repository needs to be made public prior to running the subsequent deployment.

[ryandgoulding]

I would appreciate the ability to take ownership of this issue. I am forming a PR that should help give context.

[estroz]

/assign @ryandgoulding

[estroz]

@ryandgoulding can you link your PR here? Thanks!

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[tengqm]

@ryandgoulding Would you raise a PR based on your branch? The issue is inactive for 30 days now.
/remove-lifecycle stale

[camilamacedo86]

HI @ryandgoulding,

IMO we can close it with the PR: #3555 where we are adding a quickstart more concise. See the step https://deploy-preview-3555--operator-sdk.netlify.app/docs/building-operators/ansible/quickstart/#building-and-pushing-the-project-image in the preview where your concerns raised here are addressed.

However, the "tutorials" for all types still with a ton for improvements but it shows beyond the scope of this issue. Also, please feel free to contribute with docs improvements as well.

c/c @estroz