* Exact smae file
* Added proposed list of items reqwuired to open the repo
* Addeded Steve/Service description
* Change must be lang to we would like to
* Updated checklist based on PR comments
Initial copy/commit of Elafros API design doc, chunked into sections. Also includes initial definitions of Elafros personas.
Still TODO:
- Appendices A-E, which cover extended use cases.
The certificate controller is required to configure the istio sidecar
injector webhook, but Minikube doesn't give it the paths to the CA certs
by default, so it can't start.
These paths are local to the VM, not the host machine, so they are the
same for all users.
Still few things to do but merging this to allow more people to contribute on smaller pieces
* Added issue and PR templates (#371)
* Moved PR and Issue templates to .github
* Convered Elafros overview proso to markdown
* Created overview index file and cleaned up list indents
* Object model image to the bottom
* Updated size
* Gave up, md image sizing sucks, went to HTML
* Updated headline to conform
* Updated title casing "O"
* Removed, not enough content to make it meaningful
* Removed Main Content link, file removed
There was no enough content to make this doc meaningful.
* Adde todo
* Update elafros-api-objects.md
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.
* Added port-forwarding information to telemetry documentation to prevent exposing Prometheus and Grafana publicly.
* Removed public IP option for Prometheus UI (this is mainly used for debugging and can be done using port forwarding)
* Changed the order of installation of Prometheus in the build file. Previous ordering was causing an error on a brand new cluster and required retrying the step to succeed. I still need to root cause the issue but checking this in as a mitigation/workaround for the time being.
* Adds documentation for Elafros resources
* Documents how to view just Elafros resources (#49)
* Documents how to view running pods and CRDs post-install
* Updates resources-overview documentation with recommended edits (#201)
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