Tutorial and install docs don't work well.

[schichtnudelauflauf]

What is the URL of the document?

https://sdk.operatorframework.io/docs/building-operators/golang/tutorial/
https://sdk.operatorframework.io/docs/installation/

Which section(s) is the issue in?

Create new API
and install itself

What needs fixing?

Create new API:
The thing requires "make" which is not in default install of many distros.
It fails in an annoying way because it already creates a resource in kubernetes but fails the go stuff.
If you call the command
'' $ operator-sdk create api --group cache --version v1alpha1 --kind Memcached --resource --controller) ''
again it will fail because it exists.
--force will override that and its kinda obvious but its annoying.

Install itself:
There is also a prebuilt package for Archlinux.

Additional context

None

[varshaprasad96]

@schichtnudelauflauf Having GNU make installed is usually a common practice and is implied that any operator author would be having it which is why it is not explicitly mentioned. But if that's the case otherwise, please feel free to submit a PR that adds it to the documentation.

'' $ operator-sdk create api --group cache --version v1alpha1 --kind Memcached --resource --controller) ''
again it will fail because it exists.

Regarding this, it is expected from SDK to fail when a user tries to create an API which already exists and is being tracked in the PROJECT file.

[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

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.