-
Notifications
You must be signed in to change notification settings - Fork 8
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
coordinator: make metrics endpoint configurable #491
Conversation
|
018ed18
to
83fb938
Compare
83fb938
to
4864464
Compare
4864464
to
c34e4b3
Compare
@@ -96,6 +96,7 @@ func (ct *ContrastTest) Init(t *testing.T, resources []any) { | |||
resources = kuberesource.PatchImages(resources, ct.ImageReplacements) | |||
resources = kuberesource.PatchNamespaces(resources, ct.Namespace) | |||
resources = kuberesource.PatchServiceMeshAdminInterface(resources, 9901) | |||
resources = kuberesource.PatchCoordinatorMetrics(resources, 9102) |
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.
Not sure about patching this within contrasttest
. We might want to add a test case where we disable the metrics endpoint to check it is actually not reachable. Same for the envoy admin iface or other config things. Any thoughts on this @burgerdev ?
Anyway, nothing we must address in this PR.
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.
I agree: we should eventually test these scenarios, but until then we can leave it here.
c34e4b3
to
0c5d008
Compare
0c5d008
to
a4a73d9
Compare
This makes the Coordinator metrics endpoint configurable via an environment variable. If
CONTRAST_METRICS_PORT
is set, the metrics server will start on that port. If the variable is not set, the metrics server will not start.For CI, the endpoint is activated through the
PatchCoordinatorMetrics
function.