Docs: Have an operator scope doc per type

[camilamacedo86]

Feature Request

Is your feature request related to a problem? Please describe.
Currently, we have just one doc that explains the operator scope and how to change it which is very specific for Go. However, it has been linked in the Ansible/Helm doc and then, its user may might harder to understand.

Describe the solution you'd like

• Move current the operator scope doc to Golang section
• Create one doc specific for Helm and other for Ansible in each respective sections.
• Update the links in the docs to reflect the changes.

[camilamacedo86]

For Helm/Ansible operators the steps are quite the same as Go one.
The only diff is that users will not change the main.go file which is not provided to them. However, they can do the same setup by using the WATCH_NAMESPACE as it was in the legacy layout in the config/manager/manager.yaml which allows them to inform 1 namespace or a set of them (N/Many) ( multi-namespace scenario that you can see in the Operator Scope doc for Go).

[camilamacedo86]

I just would like to track here that more than one issue came from OCP users since by the default shows that they have not admin permissions and we might need to provide in this docs a tutorial. For example, for Helm use the Nginx example to describe it.

[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

[camilamacedo86]

/lifecycle frozen