Skip to content

Conversation

@davidfestal
Copy link
Member

@davidfestal davidfestal commented Jan 25, 2023

Summary

This PR refactors the Syncer in order to make it shard-aware (supporting multiple shards)

Related issue(s)

Fixes #2832

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 25, 2023
@davidfestal davidfestal requested a review from sttts January 25, 2023 19:57
@openshift-ci openshift-ci bot requested review from jmprusi and qiujian16 January 25, 2023 19:57
@davidfestal
Copy link
Member Author

/test e2e-shared

@davidfestal
Copy link
Member Author

/test e2e-sharded e2e-shared e2e

@davidfestal
Copy link
Member Author

/test e2e-sharded

@davidfestal
Copy link
Member Author

/retest

@davidfestal davidfestal added the area/transparent-multi-cluster Related to scheduling of workloads into pclusters. label Jan 30, 2023
@davidfestal davidfestal force-pushed the shard-syncer branch 5 times, most recently from 0b4360c to 5287815 Compare January 31, 2023 14:19
@davidfestal
Copy link
Member Author

/retest

@davidfestal
Copy link
Member Author

/test e2e-sharded

1 similar comment
@davidfestal
Copy link
Member Author

/test e2e-sharded

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 8, 2023
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 1, 2023
SyncerClient kcpdynamic.ClusterInterface
SyncerDDSIF *informer.DiscoveringDynamicSharedInformerFactory
UpsyncerClient kcpdynamic.ClusterInterface
UpsyncerDDSIF *informer.DiscoveringDynamicSharedInformerFactory
Copy link
Member

Choose a reason for hiding this comment

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

what are these? Upstream/downstream? Why a new concept?

Copy link
Member Author

Choose a reason for hiding this comment

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

There are shards only for upstream (== KCP)

Copy link
Member Author

Choose a reason for hiding this comment

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

Just gathering the shard-related upstream clients and informers for both the Syncer and UpSyncer.

Naming suggestion welcomed :-)

Signed-off-by: David Festal <[email protected]>
... only temporary, before we implement
Syncer service account replication.

Signed-off-by: David Festal <[email protected]>
Signed-off-by: David Festal <[email protected]>
Signed-off-by: David Festal <[email protected]>
@davidfestal davidfestal changed the title [WIP] ✨ Syncer: support multiple shards ✨ Syncer: support multiple shards Apr 6, 2023
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 6, 2023
Signed-off-by: David Festal <[email protected]>
@ncdc
Copy link
Member

ncdc commented Apr 6, 2023

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 6, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ncdc

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 Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 6, 2023
@ncdc
Copy link
Member

ncdc commented Apr 6, 2023

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 6, 2023
@openshift-merge-robot openshift-merge-robot merged commit c04ebf8 into kcp-dev:main Apr 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/transparent-multi-cluster Related to scheduling of workloads into pclusters. kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Implement the support for several SyncTarget virtual workspace URLs (one per shard) in the Syncer

6 participants