- 
                Notifications
    You must be signed in to change notification settings 
- Fork 451
Upgrade Prometheus to v3.7.1 and resolve issues #4636
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
- Updated Prometheus to v1.8.2-0.20251020143145-59659a23710a (staleness_disabling_v3.7.1 branch) - Upgraded Loki to branch with otlptranslator v1.0.0 support and PreprocessExpr fixes - Pinned k8s.io/api, k8s.io/apimachinery, k8s.io/client-go, and k8s.io/kube-openapi to v0.32.6 versions to maintain networking/v1alpha1 API compatibility and fix structured-merge-diff v4/v6 conflicts - Fixed Mimir rulefmt.Validate to use model.UTF8Validation parameter - Removed otlptranslator replace directive (now using v1.0.0) Known issues requiring manual resolution: 1. yaml.v3 import path mismatch in k8s.io/kube-openapi (go.yaml.in vs gopkg.in) 2. OTel collector pprofile API breaking changes in debugexporter and ottl packages
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.
Some small comments.
We have the same problem as we do for #4543. That we need to partially update otel deps
| github.com/open-telemetry/opentelemetry-collector-contrib/processor/groupbyattrsprocessor v0.134.0 | ||
| github.com/open-telemetry/opentelemetry-collector-contrib/processor/intervalprocessor v0.134.0 | ||
| github.com/open-telemetry/opentelemetry-collector-contrib/processor/k8sattributesprocessor v0.134.0 | ||
| github.com/open-telemetry/opentelemetry-collector-contrib/processor/k8sattributesprocessor v0.138.0 | 
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.
Did we have to update the otel deps?
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.
Yes, some things were clashing and it was tough to resolve. In the case of k8sattributesprocessor we needed it to support k8s.io/client-go v0.34.1 which was pulled in by Prometheus.
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.
And we definitely don't want to couple the OTel upgrade with Prometheus upgrade, the change set size is already too large. So I think this is unfortunately the way forward, at least for now. In the future we can think of coordinating what versions we want to upgrade to better, so we choose versions that generate the least pain, even if they are a bit behind 🤔
        
          
                internal/component/prometheus/operator/configgen/config_gen_probe_test.go
              
                Outdated
          
            Show resolved
            Hide resolved
        
      This reverts commit 8df30f6.
PR Description
Which issue(s) this PR fixes
Notes to the Reviewer
PR Checklist