Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

componentParser: set correct target port #3141

Merged
merged 2 commits into from
Jul 16, 2024

Conversation

frzifus
Copy link
Member

@frzifus frzifus commented Jul 16, 2024

Description:

Link to tracking Issue(s):

Testing:

Documentation:

@frzifus frzifus marked this pull request as ready for review July 16, 2024 13:51
@frzifus frzifus requested a review from a team as a code owner July 16, 2024 13:51
Signed-off-by: Benedikt Bongartz <bongartz@klimlive.de>
@frzifus frzifus requested a review from jaronoff97 July 16, 2024 15:12
internal/components/component.go Outdated Show resolved Hide resolved
components.NewSinglePortParser("signalfx", 9943),
components.NewSinglePortParser("splunk_hec", 8088),
components.NewSinglePortParser("statsd", 8125, components.WithProtocol(corev1.ProtocolUDP)),
components.NewSinglePortParser("awsxray", 2000, components.WithTargetPort(2000)),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

did we need to add this everywhere?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Everywhere where we expect default ports and want to forward to the corresponding default target port.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we only need this if we expect to open a different port than the port set on the service https://stackoverflow.com/questions/49981601/difference-between-targetport-and-port-in-kubernetes-service-definition

that being said, i don't think it's going to create trouble.

Signed-off-by: Benedikt Bongartz <bongartz@klimlive.de>
@jaronoff97 jaronoff97 merged commit a515234 into open-telemetry:main Jul 16, 2024
33 checks passed
@frzifus frzifus deleted the fix_invalid_port branch July 16, 2024 15:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Invalid target port in OTEL collector SVC when endpoint and port is set in the OTLP receiver
2 participants