Tags: lovers36/ambassador
Tags
Merge pull request emissary-ingress#757 from datawire/rhs/0.39.0 Ambassador 0.39.0 release
Merge pull request emissary-ingress#755 from datawire/concaf/tests/00… …1-simple-statsd enable statsd for 001-simple
Merge pull request emissary-ingress#754 from datawire/concaf/tests/in… …crease-sleep-time increase sleep times in tests
Merge pull request emissary-ingress#751 from datawire/concaf/fix/remo… …ve-statsd-reference Remove statsd reference from template
Merge pull request emissary-ingress#724 from tech-sketch/tech-sketch/… …feature/bypass_ProtocolError catch urllib3.exceptions.ProtocolError and continue watching
Drop default statsd container Till now, Ambassador's deployment consisted of 2 containers, one ambassador container and another statsd container. This commit removes the statsd container and instead allows exposing statistics over StatsD using `STATSD_ENABLED: true` environment variable. Basically, the functionality of statsd sidecar container has been baked into the ambassdor container. Why? - The statsd container was essentially just one `socat` command. That's a lot of overhead for just one command. - An extra statsd container by default used to add confusion for the end-user who did not have a `statsd-sink` service configured because it used to continuously blurt logs complanining about the same. Now, users need to be explicit about starting `socat`. Also, now `socat` is only fired when `statsd-sink` name is resolvable by the DNS. This is checked every 4 seconds if `STATSD_ENABLED: true` is set. The DNS is no longer constantly polled by `socat`. Fix emissary-ingress#568
Merge pull request emissary-ingress#715 from datawire/concaf/release/… …0.38.0 Ambassador 0.38.0 release
Merge pull request emissary-ingress#715 from datawire/concaf/release/… …0.38.0 Ambassador 0.38.0 release
Merge pull request emissary-ingress#712 from datawire/concaf/docs/e2e… …-docs Refactor end-to-end README.md
PreviousNext