feat: change otlp http receiver port - tracing

[mat-rumian]

Description

OTLP HTTP receiver port 55681 is deprecated. OT Collector is still exposing it but soon it will be off.

Collector log:

otelcol  | 2022-03-03T13:19:33.622Z     info    otlpreceiver/otlp.go:68 Starting GRPC server on endpoint 0.0.0.0:4317   {"kind": "receiver", "name": "otlp"}
otelcol  | 2022-03-03T13:19:33.622Z     info    otlpreceiver/otlp.go:86 Starting HTTP server on endpoint 0.0.0.0:4318   {"kind": "receiver", "name": "otlp"}
otelcol  | 2022-03-03T13:19:33.622Z     info    otlpreceiver/otlp.go:141        Setting up a second HTTP listener on legacy endpoint 0.0.0.0:55681      {"kind": "receiver", "name": "otlp"}
otelcol  | 2022-03-03T13:19:33.622Z     info    otlpreceiver/otlp.go:86 Starting HTTP server on endpoint 0.0.0.0:55681  {"kind": "receiver", "name": "otlp"}

Collector version: "v0.38.1-sumo"

---

Checklist

Remove items which don't apply to your PR.

• Changelog updated

Testing performed

• Redeploy fluentd and fluentd-events pods
• Confirm events, logs, and metrics are coming in

[sumo-drosiek]

Please update changelog and add a semantic commit or PR title

[pmalek-sumo]

Apart from adding a changelog entry please add a note in description why this is needed. What caused us to change this etc.

[pmalek-sumo]

feat: change otlp http receiver port

Might be more specific so that people know it's only for tracing.

BTW: isn't that a breaking change for people already using our chart? Won't users need to adjust their setups to send on a different port?

[mat-rumian]

BTW: isn't that a breaking change for people already using our chart? Won't users need to adjust their setups to send on a different port?

No, because collector by default is opening deprecated port 55681. We are going to update our Tracing documentation with information that port 55681 will be deprecated and 4318 is the one to use.