Bump default Kubernetes to 1.29.7

[mloiseleur]

Change description

Update to latest v1.29.

Latest PR on this subject: #1450

[AverageMarcus]

I'm not sure we should skip major version when bumping. I think at the very least we should do the latest v1.29 first and then create a release of that then do another bumping to v1.30. (Edit: I just noticed that in the previous bump we did skip versions so I guess not too bad but still I think it would be best to have a specific release per version)

It's also worth being clear that v1.31 isn't officially released yet. As of 4 hours ago the second release candidate was released so it should be soon but it's still considered a pre-release and not a production release yet.

@mboersma @jsturtevant @drew-viles would be good to get your thoughts too. I don't think we've ever had anything officially wrote down for what version we target but I think we've informally followed the oldest still in support.

[drew-viles]

Yeah iirc the 13th or 14th is the target date for release of 1.31.

I'd be happy with an eventual bump to 1.30, as in I'm not against jumping a couple of versions. But, for the sake of having a sensible path of migration, I'd say we need to at least have one release with a 1.29 bump first. That way should anyone experience an issue with a 1.30 release, they have a rollback option.

[mloiseleur]

Okay, then I will update this PR to target latest v1.29

[mboersma]

/retest

Looks like a flake on Ubuntu 22.04.

[mboersma]

(BTW, the pull-ova-all job was supposed to fail starting August 1, but it seems Google gave an additional week grace period before actually pulling the plug. So test ‘em while ya got ‘em.)

[k8s-ci-robot]

@mloiseleur: 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-ova-all	5304992	link	false	/test pull-ova-all

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.

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.

[mboersma]

One of the parts of the “reset temp space” task seems to be failing, only for Ubuntu 22.04. This seems unlikely to be related to this PR, but we should investigate.

[mloiseleur]

I took some times to understand what is this test and what is happening, based on logs available in artifacts tab, here.

The ansible code for Reset temp space is here.

I'm not sure to understand why (since it's a tmpfs): it tries to delete all files in /tmp and /var/tmp

The log says it cannot on /tmp/snap.rootfs_6Priaa with errno 16 : Device or resource busy

So far, my guess is that there is a snapshot triggered or already pre-existing, and since this snapshot file is used, it cannot be deleted.

Removing the code in ansible trying to remove some tmp files would probably turn this test green, but would this be ok to remove it ?

[mboersma]

would it be ok to remove it?

I think we shouldn't, because the intent is to clean the disk image. We could maybe make it a "best effort" thing for Ubuntu 22.04 / vsphere if we can't figure out a better workaround.

I wonder if adding something like this would work:

ignore_errors: ansible_distribution_version is version('22.04', '>=')

Regardless, the pull-ova-all job has been retired now as of kubernetes/test-infra#33245, so we can't verify any changes there until there is new infrastructure behind it (see #1508).

/lgtm
/assign @AverageMarcus @drew-viles

[AverageMarcus]

/lgtm
/approve

[drew-viles]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AverageMarcus, drew-viles

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 [AverageMarcus,drew-viles]

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