Switch from localhost to 0.0.0.0 by default for all receivers

[flands]

Description: Switch from localhost to 0.0.0.0 by default

Link to tracking Issue: Addresses #592

Testing: Local

Documentation: Updated as needed

[codecov]

Codecov Report

Merging #1006 into master will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #1006   +/-   ##
=======================================
  Coverage   86.33%   86.33%           
=======================================
  Files         198      198           
  Lines       14169    14169           
=======================================
  Hits        12233    12233           
  Misses       1480     1480           
  Partials      456      456           

Impacted Files	Coverage Δ
receiver/jaegerreceiver/factory.go	91.66% <ø> (ø)
receiver/zipkinreceiver/factory.go	100.00% <ø> (ø)
internal/data/testdata/metric.go	100.00% <100.00%> (ø)
receiver/opencensusreceiver/factory.go	94.59% <100.00%> (ø)
receiver/otlpreceiver/factory.go	94.59% <100.00%> (ø)
receiver/prometheusreceiver/factory.go	81.08% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 685777f...c579c96. Read the comment docs.

[tigrannajaryan]

@flands please resolve the conflict.

[tigrannajaryan]

And fix the build, please.

[tigrannajaryan]

@flands if you will not be able to finalize this @ccaraman volunteered to help :-)

[flands]

@tigrannajaryan @bogdandrutu @jrcamp -- apologies for the delay, ready for another look.

[owais]

Can we have an env var like OPENTELEMERY_DEFAULT_LOCAL_ADDR. It can default to localhost but k8s deployment files and helm charts can change this default to 0.0.0.0. That way we'll default to localhost solving the security and macOS annoyances but still make k8s experience seamless and less confusing.

[tigrannajaryan]

Can we have an env var like OPENTELEMERY_DEFAULT_LOCAL_ADDR. It can default to localhost but k8s deployment files and helm charts can change this default to 0.0.0.0. That way we'll default to localhost solving the security and macOS annoyances but still make k8s experience seamless and less confusing.

We'll be back to the original problem when people just don't know they need to do it.

[tigrannajaryan]

@flands please resolve conflicts.

[owais]

My point was almost everywhere outside k8s, people can use localhost and for k8s we provide example config (and in near future helm charts). Such config and helm charts could default to 0.0.0.0.

[linux-foundation-easycla]

The committers are authorized under a signed CLA.

• ✅ Steve Flanders (2487a3f, 6e29eaf, c0d3146)

[tigrannajaryan]

My point was almost everywhere outside k8s, people can use localhost

@owais is this true though? If I am running a standalone Collector on a physical machine or VM how does "localhost" work? I still need to listen to external interfaces to receive connections from other machines.

[owais]

In my experience people generally put collector behind a reverse proxy like nginx or ambassador and don't expose the collector directly to the internet. But in any case, I was just throwing ideas into the mix. Not insisting we definitely do that.

[tigrannajaryan]

LGTM

[tigrannajaryan]

@flands the cla bot is not approving, not sure why. Can you retrigger the build maybe?