Update operator SDK instructions.

[smuda]

- Description of the problem which is fixed/What is the use case

The instructions for downloading the operator SDK was updated from operator SDK home page.

Fixes #263

- What I did

Updated the instructions.

- How to verify it

Follow the instructions. Notice that the file now is more than 0 bytes and also is an executable.

- Description for the changelog

Nope. I don't think this should be inserted into the changelog.

[openshift-ci]

Hi @smuda. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[bpradipt]

/lgtm
Thanks @smuda

[smuda]

/retest

[openshift-ci]

@smuda: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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.

[bpradipt]

/ok-to-test

[openshift-ci]

@smuda: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/sandboxed-containers-operator-e2e	29ca8fc	link	false	/test sandboxed-containers-operator-e2e

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[smuda]

@bpradipt Is it possible the e2e tests are a bit flunky? Both in this PR (where I only updated the markdown instructions) and #266 the same tests are failing.

Where are the e2e tests defined? I can't seem to find them in the repo and there is no information i DEVELOPMENT.md

[bpradipt]

@bpradipt Is it possible the e2e tests are a bit flunky? Both in this PR (where I only updated the markdown instructions) and #266 the same tests are failing.

Where are the e2e tests defined? I can't seem to find them in the repo and there is no information i DEVELOPMENT.md

@smuda yeah the tests are broken. The tests are here - https://github.com/openshift/release/tree/master/ci-operator/jobs/kata-containers

[littlejawa]

lgtm
Thanks @smuda