Open mboersma opened 5 months ago
This gives me the impression that maybe it's okay to ignore Prometheus dependencies if we're confident they'll get bumped transitively: https://github.com/kubernetes-sigs/cluster-api/blob/a7a32ed5705d991af0332d856f61dbcdd54abd94/.github/dependabot.yaml#L40-L41
This isn't something we would inherit automatically from CAPI, so I'll open a PR to port this over to here. I'll leave this issue open even after merging that as a reminder.
To future generations: If go.mod on the main branch ever lists github.com/prometheus/common
at v0.48.0
or higher this issue can be closed.
This isn't something we would inherit automatically from CAPI, so I'll open a PR to port this over to here.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
I think the otel dependencies at least will be ironed out in #5057, prometheus will still be an issue I think until we pull in k8s 1.31.
This is what we have queued up so far in #5057: https://github.com/kubernetes-sigs/cluster-api-provider-azure/blob/abe85cbe9854456995901be0359d8c0a574756a7/go.mod#L225-L229
/remove-lifecycle stale
/kind cleanup
What needs cleanup:
Describe the solution you'd like
Currently because of Go vendoring dependencies upstream in CAPI, the project can't ingest newer versions of
otel
or theprometheus
client libraries. The fix for that is supposedly upstream in CAPImain
now, but may wait for a new minor release before it trickles down.This issue is to remind us to revisit this once we've updated vendoring, specifically
k8s.io
packages.Anything else you would like to add:
For more context, see: