Create new document for cluster-scoped operators

[joelanford]

We currently duplicate our documentation about cluster-scoped operators in each of the three user guides (Go, Ansible, and Helm). We should abstract that documentation (and any other relevant docs, links, etc) into a separate document and link to it from each of the three user guides.

The relevant sections are:

• https://github.com/operator-framework/operator-sdk/blob/master/doc/user-guide.md#operator-scope
• https://github.com/operator-framework/operator-sdk/blob/master/doc/ansible/user-guide.md#operator-scope
• https://github.com/operator-framework/operator-sdk/blob/master/doc/helm/user-guide.md#operator-scope

[Avni-Sharma]

Hi @joelanford . I would like to take this up

[joelanford]

I know @hasbro17 was going to begin working on this, and I'm not sure if he has started yet.

@hasbro17, can @Avni-Sharma take this off your plate?

[hasbro17]

@Avni-Sharma The doc changes here depend on some CLI changes that need to be made as a result of #890
So I think it's probably best to wait until I can get those changes in first.

In the meanwhile you can probably pick up another issue like #1165 if you'd like.

[Avni-Sharma]

Sure, I would go through that

[xcoulon]

May I suggest that the document to be created also contained a comparison table of cluster-scoped vs namespace-scoped operators and cluster-scoped vs namespace-scoped CRDs?

[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

[joelanford]

This issue is closed by #1434