Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade Kubernetes Version to 1.32.2 #2521

Open
wants to merge 18 commits into
base: master
Choose a base branch
from

Conversation

Electronic-Waste
Copy link
Member

What this PR does / why we need it:

We should support the latest k8s v1.32 release https://github.com/kubernetes/kubernetes/releases/tag/v1.32.2.

Kubeflow Trainer has decided to support Kubernetes v1.32 kubeflow/trainer#2434. We'd better upgrade the Kubernetes version to maintain consistency with Trainer.

/cc @kubeflow/wg-automl-leads @helenxie-bit @mahdikhashan @Doris-xm @truc0

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #2516

Checklist:

  • Docs included if any changes are user facing

@google-oss-prow google-oss-prow bot requested review from mahdikhashan, Doris-xm, a team and helenxie-bit March 2, 2025 05:59
Copy link

@Electronic-Waste: GitHub didn't allow me to request PR reviews from the following users: truc0.

Note that only kubeflow members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

What this PR does / why we need it:

We should support the latest k8s v1.32 release https://github.com/kubernetes/kubernetes/releases/tag/v1.32.2.

Kubeflow Trainer has decided to support Kubernetes v1.32 kubeflow/trainer#2434. We'd better upgrade the Kubernetes version to maintain consistency with Trainer.

/cc @kubeflow/wg-automl-leads @helenxie-bit @mahdikhashan @Doris-xm @truc0

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #2516

Checklist:

  • Docs included if any changes are user facing

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.

Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign gaocegege for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

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

Signed-off-by: Electronic-Waste <[email protected]>
Copy link
Member Author

@Electronic-Waste Electronic-Waste left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR is ready for the review. PTAL if you have time👀

@kubeflow/wg-automl-leads @helenxie-bit @mahdikhashan @Doris-xm @truc0

Comment on lines +55 to +56
succeededBatchJobName = "test-job-succeeded"
failedBatchJobName = "test-job-failed"
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to separate the Trial run with "Failed" BatchJob. test and other tests. That's because:

  • If a Job is succeeded, we need to set Complete and SuccessCriteriaMet Conditions in the Job status
  • If a Job is failed, we need to set Failed and FailureTarget Conditions in the Job status

And we can't mutate these completion conditions, or we will get:

Invalid value: cannot disable the terminal Failed=True condition, status.conditions: Invalid value: cannot disable the terminal FailureTarget=True condition,

So we need to separate these UTs with two different Job Names.

Comment on lines 279 to 284
// TODO(Electronic-Waste): Remove this condition when K8s 1.30 is no longer supported.
// SuccessPolicy is available in K8s 1.31 and later. If we set it in K8s 1.30, it will be ignored.
// And when we set the status with `SuccessCriteriaMet`, it will report error:
// "Invalid value: cannot set SuccessCriteriaMet=True for Job without SuccessPolicy".
// REF: https://kubernetes.io/docs/concepts/workloads/controllers/job/#success-policy
isK8sVersion130 := strings.Contains(os.Getenv("KUBEBUILDER_ASSETS"), "1.30")
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to remove this when we do not plan to support Kubernetes v1.30.

Related CI error: https://github.com/kubeflow/katib/actions/runs/13613616097/job/38053846460

@Electronic-Waste Electronic-Waste marked this pull request as ready for review March 2, 2025 12:06
@Electronic-Waste
Copy link
Member Author

/rerun-all

@@ -33,7 +33,7 @@ fmt:

lint:
ifndef HAS_LINT
go install github.com/golangci/golangci-lint/cmd/golangci-lint@v1.57.2
go install github.com/golangci/golangci-lint/cmd/golangci-lint@v1.60.1
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Update this because support for Go 1.23 starts from v1.60.1

https://golangci-lint.run/product/changelog/#v1601

@Electronic-Waste
Copy link
Member Author

/rerun-all

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support Kubernetes v1.32
1 participant