Use 4 CPU nodes in setup instructions
The conformance tests have been failing and in @josephburnett 's investigation he found that it was the autoscaler changes made the tests CPU starved, and so we need beefier machines to be able to run the tests (i.e. to run elafros).
Follow up work still todo: documenting minimum system requirements.
* Remove extra _ in markdown file.
* Fix flag for running conformance tests with bazel.
* Fix conformance tests.
Commit #300 updated Route.Spec.Traffic.{Revision,Configuration} to end with Name.
1. Change - unordered list to use *
2. Change ordered lists to use lazy numbering (write 1 inline instead of
2-9)
3. Fix line lengths
4. Fix indentation on shell code sample
* Add docs for using minikube with GCR
* Add example showing creation of image pull secret
* Clarify that secrets are per-namespace
* GCR has repos, not instances
* create secrets for build-controller too
* Mention default service account and more docs
* Add env var for GCR domain
* Link to kubernetes cluster doc
* Clean up general setup steps and minikube docs
* Remove comments and correct multiline command
Comments break copy-paste
* Add documentation for creating a K8S cluster
The GKE instructions have been verified to work, but Minikube is a WIP.
* fix some formatting
* indent code block correctly
* Specify that this is Elafros-specific
Grant Rodgers