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

Multiple Release EPIC: Upgrade clusterset API to v1beta2, use the "exclusiveClusterSetLabel" as default for clusterSetType, and deprecate the "legacyclusterset" #67

Closed
11 of 12 tasks
ldpliu opened this issue Aug 11, 2022 · 9 comments
Assignees

Comments

@ldpliu
Copy link
Contributor

ldpliu commented Aug 11, 2022

By introducing a new version of clusterset api (v1beta2), we can change the migration path as below.

Release 0.9.0

Release 0.10.0

Release 0.11.0

  • Migrate storage version of clusterset api to v1beta2

Release 0.12.0

  • Remove clusterset api v1beta1
@ldpliu
Copy link
Contributor Author

ldpliu commented Aug 11, 2022

/assign @ldpliu

@elgnay
Copy link
Contributor

elgnay commented Aug 26, 2022

By introducing a new version of clusterset api (v1beta2), we can change the migration path as below.

Release N

[ ] Add exclusiveClustersetLabel selector type in clusterset api v1beta1
[ ] Add clusterset api v1beta2 to remove the support of legacyClustersetLabel selector type
[ ] Add conversion webhook to transform clusterset CRs between v1beta1 and v1beta2
[ ] Change internal consumers(ui/foundation/submarinar-addon/placement) to use clusterset api v1beta2
[ ] Other clusterset consumers (external consumers) can upgrade to clusterset api v1beta2

Release N+1

[ ] Mark clusterset api v1beta1 as deprecated
[ ] Migrate storage version of clusterset api to v1beta2
[ ] Other clusterset consumers (external consumers) must upgrade to clusterset api v1beta2

Release N+2

[ ] Remove clusterset api v1beta1

@qiujian16
Copy link
Member

/kind feature

@qiujian16 qiujian16 changed the title Use a new selectortype for clusterset selectortype by default, and deprecate the "legacyclusterset" future Multiple Release EPIC: Upgrade clusterset API to v1beta2, use the "exclusiveClusterSetLabel" as default for clusterSetType, and deprecate the "legacyclusterset" Sep 6, 2022
xuezhaojun pushed a commit to xuezhaojun/OCM that referenced this issue Mar 21, 2023
@github-actions
Copy link

This issue is stale because it has been open for 120 days with no activity. After 14 days of inactivity, it will be closed. Remove the stable label to prevent this issue from being closed.

@haoqing0110
Copy link
Member

haoqing0110 commented Aug 24, 2023

@xuezhaojun
Copy link
Member

Upgrade cluster-proxy clusterset v1beta1: open-cluster-management-io/cluster-proxy#167

Copy link

github-actions bot commented Jan 4, 2024

This issue is stale because it has been open for 120 days with no activity. After 14 days of inactivity, it will be closed. Remove the stable label to prevent this issue from being closed.

@github-actions github-actions bot added the Stale label Jan 4, 2024
@qiujian16
Copy link
Member

/close

@openshift-ci openshift-ci bot closed this as completed Jan 16, 2024
Copy link
Contributor

openshift-ci bot commented Jan 16, 2024

@qiujian16: Closing this issue.

In response to this:

/close

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.

zhujian7 pushed a commit to zhujian7/ocm that referenced this issue Jun 4, 2024
Signed-off-by: red-hat-konflux <123456+red-hat-konflux[bot]@users.noreply.github.com>
Co-authored-by: red-hat-konflux <123456+red-hat-konflux[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

5 participants