kubelet: Update deprecation messages from 1.24 to 1.25

[ialidzhikov]

/kind cleanup
/kind documentation

Similar to #106667

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[k8s-ci-robot]

Hi @ialidzhikov. 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.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[ialidzhikov]

/cc @ehashman @SergeyKanzhelev

[ehashman]

Do we have an actual target for when these are getting removed? What is the corresponding KEP?

[ialidzhikov]

Do we have an actual target for when these are getting removed? What is the corresponding KEP?

The 5 flags do not seems to be related with each other, so I doubt that we will find a KEP that unites them all.
I would rather suggest to follow-up for each of them in dedicated issues. If the flag has to be removed and its deprecation period passed, then let's remove it. Otherwise let's find out how we proceed with these deprecations, what are the blockers, define a target removal version for each of them, etch.

[pacoxu]

For this pr:

• experimental-mounter-path: gce script is still using it and there is a try to remove it in Cleanup storage related deprecated flags and default feature gate that marked as remove in 1.23 #104255 (comment)
• cloud-config and cloud-provider are used in gce scripts as well

We'd better change the log to will be removed later before gce can change the script not to use them anymore.

• experimental-allocatable-ignore-eviction can be cleanup as only usage is on in k/k https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/cloudprovider/gce/templates_test.go#L73
• experimental-kernel-memcg-notification can be removed as kernel-memcg-notification is ready.

I think we should clean up the two flags that are not used by k/k anymore.

[endocrimes]

/lgtm
/triage accept
/priority important-soon

[k8s-ci-robot]

@endocrimes: The label(s) triage/accept cannot be applied, because the repository doesn't have them.

In response to this:

/lgtm
/triage accept
/priority important-soon

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[endocrimes]

/triage accepted

[SergeyKanzhelev]

/ok-to-test
/lgtm
/retest

just a user friendly text update. Looks good

[pacoxu]

/assign @mrunalp

[SergeyKanzhelev]

/lgtm

re-applying

[endocrimes]

/cc @dims @derekwaynecarr

[dims]

just bumping version numbers. happy to land this.

/approve
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dims, endocrimes, ialidzhikov, SergeyKanzhelev

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:

• cmd/kubelet/OWNERS [dims]

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