-
Couldn't load subscription status.
- Fork 35
add epp servicemonitor #87
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
Conversation
fd454d5 to
7fb5c09
Compare
|
Is the intent of this to add monitoring to the epp node itself? |
|
I notice the creation of a |
|
With a push to move function to the upstream GAIE, I wonder if this should be there instead? |
a24687c to
705ade9
Compare
|
@kalantar servicemonitor with rbac/bearertoken is required to scrape metrics from EPP - the equivalent changes are proposed in the GAIE charts (kubernetes-sigs/gateway-api-inference-extension#1425) - yes if charts are moved upstream, this won't be required. This change will enable metrics collection from EPP pod until the charts are consolidated into 1 upstream chart. Clusterrole & Clusterrolebinding are required to scrape metrics from EPP. Same as in GAIE charts. |
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.
Tracking the upstream GAIE PR. It sounds like once that is merged, this PR against ms won't be necessary.
Signed-off-by: sallyom <[email protected]>
705ade9 to
947a931
Compare
|
@kalantar @jgchn upstream PR merged - the wide-ep guide deploys epp with modelservice charts, so we should add the servicemonitor to modelservice charts as well since these will remain through the next release. PR to add servicemonitor to guides /cc @Gregory-Pereira |
|
closing this, will look at new format for kustomize |
Adds EPP servicemonitor