It seems to me that calling 'sudo' is not necessary at this point. In fact, if kubernetes hasn't been built yet, this will result in _output/ folder being owned by root thus making it not possible to run other consequent commands without 'sudo'.
Currently if you follow this guide when it comes to starting nginx you get this error:
Error starting userland proxy: listen tcp 0.0.0.0:8080
Because Kubernetes is already listening on :8080, so you can't bind nginx to :8080, so I've changed it to :8081
While the linux dependency is obvious with a moment's thought, some
users (especially on *nix) might plow ahead before realizing their
system isn't supported. This adds a requirements section and points
users in the direction of guides more likely to work for them.
The project README is getting quite large mainly because of all
the getting started guides embedded in the README.
Create the docs/getting-started-guides directory and relocate all
getting started guides. Update the README to link to each getting
started guide.
