1.29: housekeeping tasks

[chendave]

This is a tracking issue for tasks that we are required to carry out during each cycle. It tracks the upcoming release of Kubernetes 1.29 (1.x)

Note: make sure you reference this issue in PRs.

same issue for 1.x-1 (see example PRs): #2857

When 1.x-4 version goes out of support https://kubernetes.io/releases/#release-history

• Drop kinder support for 1.x-4 and older (may not be needed every release)
  there are some TODOs for 1.25\

• kinder: remove the handling of 1.25 and older versions of k8s #2966

• Vendor the latest system-validators in kubernetes/kubernetes (may not be needed every release)
• Cleanup E2E jobs for 1.x-4 (requires two PRs)
  set KUBERNETES_VERSION to 1.x-1 and KUBERNETES_SKEW to 3 in /kinder/hack/update-workflows.sh
  make sure PATH_TEST_INFRA points to the right path.
  run the script and send two PRs for k/kubeadm and k/test-infra.
  See KEP-3935: Generate test configurations for n-3 node skew #2855

When the release-1.x branch and release-1.x test dashboards are created

• Create E2E jobs for 1.x
  set KUBERNETES_VERSION to 1.x and KUBERNETES_SKEW to 3 in /kinder/hack/update-workflows.sh
  make sure PATH_TEST_INFRA points to the right path.
  run the script and send two PRs for k/kubeadm and k/test-infra.

• kubeadm: update kinder test job for k8s 1.29 test-infra#31194
• kinder: update test workflow for 1.29 #2956

Before the 1.x+1 cycle start

• Duplicate this issue for tracking 1.x+1 housekeeping tasks
• Close this issue

[chendave]

/help wanted

[chendave]

/help

[k8s-ci-robot]

@chendave:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

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.

[liangyuanpeng]

I want to try it and I will use the PR of v1.28 as a reference.

/assign

[neolit123]

/assign

the release-1.29 branch creation is scheduled for ~21st of Nov

[liangyuanpeng]

I' m come back after code freeze for 1.29 and still want to try it.
I cane see the below task need to work for 1.29:

• Update github action workflow for 1.29, same with KEP-3935: Generate test configurations for n-3 node skew #2855
• Update test-infra for KEP-3935, same with: KEP-3935: update test configurations for n-3 node skew test-infra#29287
• Add test github workflow for 1.29, same with kinder: add test workflows for 1.28 #2906

I'm looking forward to knowing if I can try it out and need some guidance on that. Remind me if i missed something,Thanks :)

@neolit123

[chendave]

@liangyuanpeng feel free to go, there is a script(/kinder/hack/update-workflows.sh) can generate those change I believe, so it's pretty lightweight change I think.

[chendave]

/assign @liangyuanpeng

[chendave]

/unassign @neolit123

[liangyuanpeng]

I have create a PR #2956 for it and i think have not script to generate files for kubernetes/test-infra side, right? Thanks.

[neolit123]

the new PRs seem fine but they must be on hold until 21s Nov

When the release-1.x branch and release-1.x test dashboards are created

[neolit123]

1.30
#2982