/triage accepted

Hi @tallclair!
My name Hossein Salahi from Bug-Triage team. I am just checking to ensure if everything is on track for K8s 1.25.
Thanks!

@encodeflush I think so, but this isn't user facing so it's not a big deal if it slips to v1.26.

/milestone clear

/milestone v1.26

I'd like to try and get this in the next release.

Hi @tallclair, member of the bug triage team for 1.26 here! I just wanted to check whether this issue is on track for the 1.26 release.

Thank you!

I'm still hoping to get it in this release, but blocked on approval on #111095.

Note that this is just a cleanup, so no real impacts of this slipping if it doesn't make the cutoff.

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

/remove-lifecycle stale

I'm still working on this. Will make some progress this release, though it might not be completed until v1.28.

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

/triage accepted