You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 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.
Before the 1.x+1 cycle start
Duplicate this issue for tracking 1.x+1 housekeeping tasks
Close this issue
The text was updated successfully, but these errors were encountered:
@pacoxu:
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.
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.
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.32 (1.x)
Note: make sure you reference this issue in PRs.
same issue for 1.x-1 (see example PRs): #3047
When 1.x-4 version goes out of support https://kubernetes.io/releases/#release-history
When the release-1.x branch and release-1.x test dashboards are created
set
KUBERNETES_VERSION
to 1.x in /kinder/hack/update-workflows.shmake sure
PATH_TEST_INFRA
points to the right path.run the script and send two PRs for k/kubeadm and k/test-infra.
Before the 1.x+1 cycle start
The text was updated successfully, but these errors were encountered: