Please note that we're already in Test Freeze for the release-1.30 branch. This means every merged PR will be automatically fast-forwarded via the periodic ci-fast-forward job to the release branch of the upcoming v1.30.0 release.

Fast forwards are scheduled to happen every 6 hours, whereas the most recent run was: Wed Apr 17 07:56:14 UTC 2024.

Hi @jwcesign. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

/cc @liggitt

Can you please take a look? Thank you.

@dims Hi, can you help take a look about this?

like #119312, you need run

hack/pin-dependency.sh github.com/prometheus/common v0.48.0
hack//update-vendor.sh
hack//lint-dependencies.sh

@pacoxu Thanks for helping!

Should I do something with this Note?

root@play [21:56:01] [~/git/kubernetes] [master *]
-> # hack/update-vendor.sh
+++ [0418 21:56:50] logfile at /tmp/update-vendor.7OL2/update-vendor.log
+++ [0418 21:56:50] go.mod: update staging references
+++ [0418 21:57:11] go.mod: propagate to staging modules
+++ [0418 21:57:17] go.mod: sorting staging modules
+++ [0418 21:57:57] go.mod: tidying
+++ [0418 21:59:53] go.mod: adding generated comments
+++ [0418 21:59:55] vendor: updating internal modules
+++ [0418 22:00:47] vendor: running 'go work vendor'
+++ [0418 22:00:53] vendor: updating vendor/LICENSES
+++ [0418 22:01:03] vendor: creating OWNERS file
+++ [0418 22:01:03] NOTE: don't forget to handle vendor/* and LICENSE/* files that were added or removed

https://github.com/kubernetes/kubernetes/blob/e6efba3380c87503f918053c0511587485a2f828/hack/update-vendor.sh#L433-L434

As the note say, you can ignore it if you do not add a new dep or remove one.
You can just run hack/update-vendor-licenses.sh to confirm(there should be no change after running it).

BTW, code block using ``` is preferred than screenshot. It's not convenient to copy-paste from a screenshot.

/lgtm
/approve
for sig-instrumentation

LGTM label has been added.

/test pull-kubernetes-e2e-kind-ipv6

/cc @smarterclayton @alexzielenski
Hi, can you help checking about the e2e modification, thanks!

/lgtm
after rebase
/assign @dims @liggitt

LGTM label has been added.

One library down :) checked the diffs, looks good to me.

/approve
/lgtm

--- /logs/artifacts/stats-base.txt	2024-04-20 01:56:06.203450224 +0000
+++ /logs/artifacts/stats.txt	2024-04-20 01:55:59.953379917 +0000
@@ -1,4 +1,4 @@
-Direct Dependencies: 199 
+Direct Dependencies: 198 
 Transitive Dependencies: 332 
 Total Dependencies: 377 
 Max Depth Of Dependencies: 24 

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dashpole, dims, jwcesign, logicalhan

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

The pull request process is described here

Any chance this will be cherry-picked to v1.30?

Any chance this will be cherry-picked to v1.30?

likely not... we don't generally bump dependencies on release branches unless required for security fixes