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
Add ServiceMonitor config for Agent Envoy when enabled #30126
Conversation
/test |
Will we be able to backport this to 1.14? AFAICT, we should, as it's a bug fix for the Helm chart. If so, 🤞 so that we get this into the next January 24 patch release. |
f686a9f
to
10c0e72
Compare
I've marked this for backport, it makes sense for me. |
/test |
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.
nice, thanks @youngnick !
ci-ipsec-upgrade hit #27762. |
/ci-ginkgo |
Checking to see if it's the same two ginkgo jobs failing. |
/ci-ginkgo |
the Ginkgo check keeps failling at different steps for different reasons, I'll try one last time |
/ci-ginkgo |
This commit adds Prometheus config to scrape Envoy metrics from the Envoy port (default 9964) on the Agent when Envoy is enabled. It uses the newer `.Values.envoy` section of the Helm chart, as we want to emphasize using that config regardless of where Envoy is running (in-agent or in a separate Daemonset). Signed-off-by: Nick Young <nick@isovalent.com>
10c0e72
to
2b11269
Compare
/test |
/ci-e2e |
This commit adds Prometheus config to scrape Envoy metrics from the Envoy port (default 9964) on the Agent when Envoy is enabled.
It uses the newer
.Values.envoy
section of the Helm chart, as we want to emphasize using that config regardless of where Envoy is running (in-agent or in a separate Daemonset).Fixes: #28356