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

OpenCensus port is not exposed by the Collector Service #295

Closed
thib92 opened this issue May 26, 2021 · 2 comments · Fixed by #299
Closed

OpenCensus port is not exposed by the Collector Service #295

thib92 opened this issue May 26, 2021 · 2 comments · Fixed by #299
Labels
bug Something isn't working good first issue Good for newcomers

Comments

@thib92
Copy link
Contributor

thib92 commented May 26, 2021

Hello,

I am deploying an OpenTelemetry Collector with an OpenCensus receiver.
According to the comments on the ports parameter, the operator should be able to detect well-known protocols in the config and expose their port. However, after deploying it, the collector initializes the OpenCensus receiver, but the service is not updated to expose the OpenCensus port.

It should be noted that the collector was first declared and deployed with only an oltp receiver, and I later updated it to add the OpenCensus collector. Maybe the operator simply didn't update the service.

@bhiravabhatla
Copy link
Contributor

Yep - you are right - On update the exposed ports are not getting updated. We have an open issue for the same.

#256

I was supposed to fix this, but have been occcupied in some other work. Feel free to raise a PR for this.

@jpkrohling jpkrohling added bug Something isn't working good first issue Good for newcomers labels May 27, 2021
@thib92
Copy link
Contributor Author

thib92 commented May 27, 2021

I'm going to give it a try. It doesn't seem too hard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants