feat: add interface ClusterProvider #37
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
shaofan-hs
force-pushed
the
cluster-controller
branch
5 times, most recently
from
4e590a0
to
eb903ea
Compare
zoumo
changed the title
shaofan-hs
force-pushed
the
cluster-controller
branch
3 times, most recently
from
0542ffe
to
0b6fd4e
Compare
shaofan-hs
changed the title
zoumo
reviewed
Mar 21, 2024
multicluster/manager.go
Outdated
| type ManagerConfig struct { | ||
| FedConfig *rest.Config | ||
| ClusterScheme *runtime.Scheme | ||
| controller.ClusterProvider | ||
| ClusterProvider |
There was a problem hiding this comment.
ClusterProvider ClusterProvider
or
Provider ClusterProvider
shaofan-hs
force-pushed
the
cluster-controller
branch
2 times, most recently
from
7968706
to
6591737
Compare
shaofan-hs
force-pushed
the
cluster-controller
branch
from
6591737
to
00dcda6
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):
re #38
2. What is the scope of this PR (e.g. component or file name):
3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):
4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):
5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:
6. Release note
Please refer to Release Notes Language Style Guide to write a quality release note.