* Hide finder indexes
* Remove samples from serving
* Add back the helloworld sample
* Link to docs repo
* Move build-pack samples
* Clean up merge
* Remove helloworld again
* Move to using Istio v1alpha3 API.
* Removing ingressInformer from controllers since we no longer need.
* Update typo and utilization target for HPA.
* Add README.md to explain how we create these types.
* Update per PR feedback
* Update per PR feedback.
* Add back the timeout settings.
The timeout headers were added when we used v1alpha2 in order to allow
more time for 0->1 scaling. I accidentally undo that change when
moving to v1alpha3. This adds it back.
* Run hack/update-codegen.sh.
* Update per PR feedback.
* Update per PR feedback.
* Update per PR feedback.
We don't own `demo-domain.com`, so configuring it by default presents an abundance of problems. `example.com` is the canonical placeholder domain, so we will configure that by default.
In the future we will very likely change this to a sane default that will automatically work with intra-cluster DNS, but until then this seems like the most reasonable default.
Fixes: https://github.com/knative/serving/issues/1365
* Adds sample gRPC application
* this sample depends on https://github.com/knative/serving/issues/1047 to be complete
* * Adds '-insecure' flag to sample grpc client
* Adds comment that the sample grpc server serves h2c by default
* add sample apps for Elafros routing
* temporary debug
* add Ingress and RouteRule to route request according to uri
* Reverse back some code for debugging
* Rename files and fix typepo
* Add some content in README
* add some space
* add ADDRESS and PORTS
* add space
* add space
* delete space
* add space
* add space
* add ADDRESS and PORTS for search
* add ADDRESS and PORTS for entry
* Add content of Exploring section in README.md
* Fulfill the section of How It Works
* fix typos
* revert unnecessary file
* Fix typos
* fix the incorrect container image path
* fix the incorrect container image path
* 1. Add comment in routing.yaml file. 2. Use Elafros service instead of Route and Configuration in sample.yaml 3. Delete Dockerfile and reuse sample/Dockerfile.golang 4. Rewrite README and add a graph
* fix typos
* replace elafros with knative
* delete old paths
* enforce the 80 char a line
* enforce the 80 char a line
* rephrase README
* fix typo of apiVersion after renaming elafros to knative
* Move revision condition manipulation into revision_types.go
This is the Revision equivalent of #1113
This contains two other unrelated changes:
1. Condense the object construction in `revision_test.go`
1. Reorder the `helloworld` yaml to create the configuration first.
The reason for the second "unrelated" change is that I was seeing the route controller marking the Route as "AllTrafficAssigned = False" because the configuration wasn't created yet.
* Update the conditions spec to eliminate wording about elision.
Eliding conditions can come later, it's a premature optimization,
and I'm not sure we're handling conditions well enough to do it
reliably yet.
* Fix test breakages due to setCondition becoming private.
* Add unit test coverage of the condition logic.
* Clarify isBuildDone through local variable names.
* Rename most ela-* things
Left `ela-prow` since that is an external dependency that might break.
* Fix filenames
* Revert some e2e test changes
* attempt to fight the Walk function
* Address feedback
* Rearrange yaml order
Attempt to reflect the important-looking order from bazel's build rules.
See: a15e38795b/config/BUILD.bazel (L121-L138)
Other Knative projects use the project name in the CRD group. Now that
the Serving project is no longer called "elafros", the project name
should be included in the CRD group namespace.
This is a breaking change, but aligns well with the other breakages
caused by the rename.
I intentionally did not update name for resource labels or for logging.
In docs there were a few references to CRDs from the build project.
Those CRD groups are now called build.knative.dev.
* elafros/elafros -> knative/service
* replace elafros with knative
* changed ela package to serving
* change elafros/build to knative/build and newer version
* things are running mostly
* address build / test failures
* address integration test failures
* repo has not chnaged
* Remove the usage of prometheus operator and manage prometheus instances ourselves. This is needed because prometheus operator doesn't work with kubernetes 1.10 yet and we need that support. We are not making use of prometheus operator capabilities yet, so there is no functionality lost.
* Add OWNERS files to monitoring related folders.
* Consolidate the Dockerfile used for the assorted Go samples.
* Samples should use multi-stage Dockerfile build.
This better reflects what contributors see with bazel/ko and best practices for image construction.
Fixes: https://github.com/elafros/elafros/issues/927
* Cleanup OWNERS files
* removed OWNERS files from //vendor, as they contain external approvers unrelated to Elafros
* added headers to all existing OWNERS files
* removed CODEOWNERS
* updated documentation, updating all references from CODEOWNERS to OWNERS
* Update update-deps.sh to also remove OWNERS files from deps
The buildpack-function sample uses the buildpack build template with a
custom buildpack that uses the projectriff node-function-invoker to
host the projectriff node-square sample function into a container that
confirms to the Elafros container spec.
Synced the buildpack build template from elafros/build-templates.
* Use import paths as placeholders for our development flow.
This change adopts the convention of replacing our current placeholder image names (e.g. "ela-queue:latest", which clearly don't exist on DockerHub) with the convention of using the Go import path for the binary that we will containerize and substitute.
I find this convention makes the source of the image clearer, but this is also part of a larger experiment (called `ko`) to explore ways to hedge our bets around Bazel for a faster development flow.
We need to restructure our configs a bit to get a flow equivalent to `:elafros.apply`, but this change is enough to make this work for individual files:
```shell
$ ko apply -f controller.yaml
2018/04/27 08:17:27 Go building github.com/elafros/elafros/cmd/ela-controller
2018/04/27 08:17:27 Go building github.com/elafros/elafros/cmd/ela-autoscaler
2018/04/27 08:17:27 Go building github.com/elafros/elafros/cmd/ela-queue
2018/04/27 08:17:35 Publishing us.gcr.io/convoy-adapter/github.com/elafros/elafros/cmd/ela-autoscaler:latest
2018/04/27 08:17:35 Publishing us.gcr.io/convoy-adapter/github.com/elafros/elafros/cmd/ela-queue:latest
2018/04/27 08:17:36 mounted sha256:eb05f3dbdb543cc610527248690575bacbbcebabe6ecf665b189cf18b541e3ca
2018/04/27 08:17:36 mounted sha256:28ccb4f090043ed4b3e33f78c7834f1e3a97ea0af098dbb326b646c7db68d963
2018/04/27 08:17:36 mounted sha256:8d7d4db448cf93a94bee252850cc619b63873158ae918577f29f3cf0d3c4d090
2018/04/27 08:17:36 mounted sha256:abd64b9bfa74a9afd2a24b87db49f388ea9b9b7a6712a0d12bfd0e53b2c0a900
2018/04/27 08:17:36 mounted sha256:eb05f3dbdb543cc610527248690575bacbbcebabe6ecf665b189cf18b541e3ca
2018/04/27 08:17:36 mounted sha256:fdf0520392d40ef7658a5807c5fc1cde837132c0ea62dc91050b2d1b95e412b7
2018/04/27 08:17:36 Publishing us.gcr.io/convoy-adapter/github.com/elafros/elafros/cmd/ela-controller:latest
2018/04/27 08:17:36 mounted sha256:eb05f3dbdb543cc610527248690575bacbbcebabe6ecf665b189cf18b541e3ca
2018/04/27 08:17:36 pushed us.gcr.io/convoy-adapter/github.com/elafros/elafros/cmd/ela-autoscaler:latest
2018/04/27 08:17:36 Published us.gcr.io/convoy-adapter/github.com/elafros/elafros/cmd/ela-autoscaler@sha256:034b8254249f5fffc3888e5a23f8d8376df60bb8476dcbafe86b17b57f2568a9
2018/04/27 08:17:36 pushed us.gcr.io/convoy-adapter/github.com/elafros/elafros/cmd/ela-queue:latest
2018/04/27 08:17:36 Published us.gcr.io/convoy-adapter/github.com/elafros/elafros/cmd/ela-queue@sha256:c258c53faa724e1c2af7db6c00bf6b347d8b4392349ca9867493b32e9176504b
2018/04/27 08:17:36 mounted sha256:033b2da213a6858a05e109da8548b75f59eaf3729c49d6126b4b505e35067a28
2018/04/27 08:17:36 mounted sha256:d1b13624a3d517c95b3f26d6532f25b261887f1e0a5da26349ba844b2ac956b4
2018/04/27 08:17:37 pushed us.gcr.io/convoy-adapter/github.com/elafros/elafros/cmd/ela-controller:latest
2018/04/27 08:17:37 Published us.gcr.io/convoy-adapter/github.com/elafros/elafros/cmd/ela-controller@sha256:1aafac2f20a7a2b1c9435af4f7dbfa9db4f85f8c18dcb6850f9a9dc11f55d059
deployment "ela-controller" unchanged
```
Eventually, I hope to restructure our configs to enable (something like): `ko apply -R -f config/`
* Update the samples as well.
Fixes#703
When we migrated from OpenZipkin to OpenCensus libraries, the distributed traces started to appear different than with OpenZipkin. Investigating this with OpenCensus team, it turns out that Open Zipkin closes spans at the end of RoundTrip method vs res.Body.Close() for OpenCensus. OpenCensus' behavior is the correct one here: In our code, instead of using defer res.Body.Close(), we need to do res.Body.Close in order to correctly calculate the span timing information.
Nader Ziada
Markus Thömmes
Sam O'Dell
Ryan Gregg
Jason Hall
Nghia Tran
Matt Moore
jonjohnsonjr
Brenda Chan
Steren
Evan Anderson
Yanwei Guo
Zhimin Xiang
Scott Andrews
Ville Aikas
Mustafa Demirhan
David Protasowski
Adriano Cunha
Joseph Burnett