Repository navigation
Add optional ServiceMonitor in flyte-binary - #8154
Merged
Sovietaced merged 1 commit intoOct 12, 2026
Merged
Sovietaced merged 1 commit into
Sovietaced merged 1 commit into
Conversation
Sovietaced
approved these changes
Oct 9, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #8154 +/- ##
==========================================
- Coverage 57.33% 57.32% -0.02%
==========================================
Files 931 931
Lines 58331 58331
==========================================
- Hits 33445 33439 -6
- Misses 21833 21839 +6
Partials 3053 3053
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Signed-off-by: ChickenBenny <zxc123benny14159@gmail.com>
Sovietaced
force-pushed
the
feat/6437-flyte-binary-servicemonitor
branch
from
October 12, 2026 16:54
23e6cdb to
05bbcef
Compare
davidmirror-ops
approved these changes
Oct 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Tracking issue
Closes #6437
Why are the changes needed?
The monitoring docs tell flyte-binary users to expose an
http-metricsport (10254) and say this"enables the serviceMonitor", but the flyte-binary chart doesn't ship a
ServiceMonitor, so usershave to write their own (as
flyte-corealready provides one per component).What changes were proposed in this pull request?
templates/service-monitor.yamlto the flyte-binary chart, gated byserviceMonitor.enabled(default
false, so clusters without the Prometheus Operator CRDs are unaffected).serviceMonitor.{enabled, interval, scrapeTimeout, labels}tovalues.yaml.flyte-binary.baseLabels(name+instance).selectorLabelscan't be usedbecause it includes
app.kubernetes.io/component, which the Services don't carry.How was this patch tested?
helm templatewith default values: no ServiceMonitor rendered.helm templatewithserviceMonitor.enabled=true+service.extraPorts(http-metrics: 10254):the ServiceMonitor's
matchLabelsmatch the http Service's labels, and the Service exposeshttp-metrics.helm lintpasses;make helmproduces no changes to generated manifests.Labels
Setup process
Screenshots
N/A
Check all the applicable boxes
Related PRs
N/A
Docs link
Changed:
docs/deployment/configuration/monitoring.rst(Prometheus setup → flyte-binary tab)