[kong] target proxy with ServiceMonitor selector #112
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit limits the ServiceMonitor, so it only targets the proxy
Service resource instead of both the proxy and the admin Service.
What this PR does / why we need it:
When we set
serviceMonitor.enabled
totrue
, aServiceMonitor
resource is created, which targets both the adminService
and the proxyService
. The metrics are identical, which means they're doubled in in Prometheus. This change makes it so theServiceMonitor
only targets the proxyService
.Special notes for your reviewer:
I didn't know which label we'd think would be appropriate, and since naming is hard, I opted to throw a strawman label into this PR, so we could discuss what we want here.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]
next
branch and targetsnext
, notmaster
[kong]
)