Automated cherry pick of #17792: aws: Disable the kubelet systemd unit during warm pool warming

[dezmodue]

Cherry pick of #17792 on release-1.32.

#17792: aws: Disable the kubelet systemd unit during warm pool warming

For details on the cherry pick process, see the cherry pick requests page.

[k8s-ci-robot]

Hi @dezmodue. Thanks for your PR.

I'm waiting for a github.com 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.

Details

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-sigs/prow repository.

[dezmodue]

@hakman - created cherry pick for 1.32 as discussed, thanks.

[hakman]

/ok-to-test
/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hakman

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [hakman]

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

[hakman]

/test pull-kops-e2e-k8s-aws-cilium-1-32

[k8s-triage-robot]

Retesting failed PR that otherwise appears ready for merge.

Please help us fix flaky tests by following our Flaky Tests Guide.

Prevent this bot from retesting with /lgtm cancel or /hold.
For this robot's configuration, see here.

/retest-required

[dezmodue]

I checked the failed tests but I don't think they are correlated to this PR.

[hakman]

I checked the failed tests but I don't think they are correlated to this PR.

No worries, this is one of the reasons I was saying that it may not be easy to do a new 1.32 release.

[hakman]

/override tests-e2e-scenarios-bare-metal

[k8s-ci-robot]

@hakman: Overrode contexts on behalf of hakman: tests-e2e-scenarios-bare-metal

Details

In response to this:

/override tests-e2e-scenarios-bare-metal

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-sigs/prow repository.

[hakman]

@dezmodule Could you re-create the PR? Tests should pass after that.

[hakman]

/lgtm cancel

[k8s-ci-robot]

@dezmodue: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-kops-e2e-k8s-aws-cilium-1-32	5065668	link	true	/test pull-kops-e2e-k8s-aws-cilium-1-32

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

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-sigs/prow repository. I understand the commands that are listed here.

[dezmodue]

Will re create as requested