-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Deprecate ProvisioningRequest v1beta1 #8549
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
Conversation
Welcome @partykamdev! |
Hi @partykamdev. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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 PR may require API review. If so, when the changes are ready, complete the pre-review checklist and request an API review. Status of requested reviews is tracked in the API Review project. |
/ok-to-test |
/release-note-none |
@jackfrancis: you can not set the release note label to "release-note-none" because the PR has the label "kind/deprecation". In response to this:
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. |
/release-note-edit
|
// +kubebuilder:printcolumn:name="Age",type="date",JSONPath=".metadata.creationTimestamp" | ||
// +k8s:deepcopy-gen:interfaces=k8s.io/apimachinery/pkg/runtime.Object | ||
// +k8s:prerelease-lifecycle-gen:introduced=1.29.0 | ||
// +k8s:prerelease-lifecycle-gen:deprecated=1.35.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@partykamdev @towca should we mark this as deprecated in 1.34.0 and include in v1.34.0 release?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This could be deprecated in v1.34.0, updated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1, that would be ideal. @BigDarkClown is just starting the release, let's merge this quickly.
cluster-autoscaler/apis/config/crd/autoscaling.x-k8s.io_provisioningrequests.yaml
Outdated
Show resolved
Hide resolved
/label tide/merge-method-squash |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: partykamdev, towca 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:
Approvers can indicate their approval by writing |
Deprecate ProvisioningRequest v1beta1 (#8549)
* deprecate * fix
What type of PR is this?
/kind cleanup
/kind api-change
/kind deprecation
What this PR does / why we need it:
v1 ProvisioningRequest has already been available for over a year and should be deprecated as per https://kubernetes.io/docs/reference/using-api/deprecation-policy/
Does this PR introduce a user-facing change?
Users will now see
v1beta1 ProvisioningRequest is deprecated
message when using v1beta1 ProvisioningRequest.