-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Fix k8s pulsar functions containers not exposing metrics port for scraping #12065
Fix k8s pulsar functions containers not exposing metrics port for scraping #12065
Conversation
… their metrics port for scraping
@sijie would you mind approving the workflows/tests to be run? 🙏 |
can this be reviewed/merged? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Closing and reopening to trigger CI. All of the tests are in "Expected" state. I haven't seen this happen before. |
Alright, tests are listed as "Queued", so they should run. |
/pulsarbot run-failure-checks |
Unfortunately, we have some flaky tests. The test that failed is not related to this change. Re-running the failed test. |
(cherry picked from commit 4dd4bd6)
(cherry picked from commit 4dd4bd6)
@volgorean - thanks for your contribution! I cherry picked it to the relevant branches. |
(cherry picked from commit 4dd4bd6)
Motivation
Modifications
getFunctionContainerPorts
to return both its grpc port as well as the metric port (currently the function returning the metrics port in its own list is not being called)Verifying this change
This change added tests and can be verified as follows:
Documentation