Skip to content

remove unused configuration of MultiClusterService #211

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

umangachapagain
Copy link
Contributor

MirrorPeer.Spec.OverlappingCIDR was added to allow users to automatically enable StorageCluster.Spec.Netowrking.MultiClusterService when needed. But this implementation had some limitations due to which it was not generally used.

This commit now drops the changes completely to avoid unwanted usage. This will be replaced by alternate solutions which are more reliable.

MirrorPeer.Spec.OverlappingCIDR was added to allow users to automatically
enable StorageCluster.Spec.Netowrking.MultiClusterService when needed. But
this implementation had some limitations due to which it was not generally
used.

This commit now drops the changes completely to avoid unwanted usage. This
will be replaced by alternate solutions which are more reliable.

Signed-off-by: Umanga Chapagain <[email protected]>
Copy link
Contributor

openshift-ci bot commented Jun 7, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: umangachapagain

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved label Jun 7, 2024
@umangachapagain
Copy link
Contributor Author

/test integration-test

@vbnrh
Copy link
Member

vbnrh commented Jun 10, 2024

@umangachapagain WIll there be any impact for people already using it ?

@umangachapagain
Copy link
Contributor Author

umangachapagain commented Jun 10, 2024

@umangachapagain WIll there be any impact for people already using it ?

There shouldn't be any impact other than the fact that it will stop working. If MultiClusterService is already enabled, it will not be disabled after this. If it is disabled, it can not be enabled with this feature and needs to be enabled using other ways.

@vbnrh
Copy link
Member

vbnrh commented Jun 11, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm label Jun 11, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit acfbd5a into red-hat-storage:main Jun 11, 2024
11 checks passed
@umangachapagain umangachapagain deleted the remove-MultiClusterService-automation branch June 11, 2024 07:26
@umangachapagain
Copy link
Contributor Author

/cherry-pick release-4.16

@openshift-cherrypick-robot

@umangachapagain: new pull request created: #212

In response to this:

/cherry-pick release-4.16

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.

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

Successfully merging this pull request may close these issues.

3 participants