🌱 Downgrade prometheus client libs to versions used in k/k 1.30

[sbueringer]

Signed-off-by: Stefan Büringer buringerst@vmware.com

[sbueringer]

/assign @vincepri @alvaroaleman

We recently had some problems when upgrading even further. But I think we should play it safe and use the exact same versions that k/k is using.

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: b8da5868640810a3dba865a8f7a3d29ee927ff88

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alvaroaleman, sbueringer

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [alvaroaleman,sbueringer]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[aerfio]

We recently had some problems when upgrading even further. But I think we should play it safe and use the exact same versions that k/k is using.

@sbueringer could you please provide a link to an issue/PR which explains those problems? Thanks

[vincepri]

As a general rule we match controller-runtime dependencies with upstream ones, if possible. @sbueringer we might want to add a validation script to keep them in sync

[sbueringer]

@aerfio The initial problem we found in this context was this: #2750

Nobody complained yet about the diff we had after this PR, but it might just be a matter of time until someone uses another package where additional errors pop up. So to play it safe we try to keep the dependencies in sync to avoid compile errors when folks start adopting a new CR version