-
Notifications
You must be signed in to change notification settings - Fork 380
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
Add scope
field for toServices
in Antrea-native policies
#4397
Conversation
Codecov Report
@@ Coverage Diff @@
## main #4397 +/- ##
==========================================
+ Coverage 69.78% 70.02% +0.24%
==========================================
Files 379 391 +12
Lines 55438 55532 +94
==========================================
+ Hits 38688 38887 +199
+ Misses 14081 13981 -100
+ Partials 2669 2664 -5
*This pull request uses carry forward flags. Click here to find out more.
|
@Dyanngg Could you re-base and resolve conflicts? thanks. |
36a37b9
to
4425556
Compare
4425556
to
8946080
Compare
@Dyanngg could you address the remain comments? I think overall is good, we may merge this after you address the comments. thanks. |
a31fc9f
to
b089a0c
Compare
@Dyanngg there is an out-of-date manifest, please check and fix it. https://github.com/antrea-io/antrea/actions/runs/3699555406/jobs/6267162564 |
LGTM, one minor comment |
@tnqn : is it an incompatible API change? Or, we do not consider client lib changes in versioning? |
This only adds an optional field and is compatible. If you mean the type change NamespacedName -> PeerService, I think it's fine. If the lib consumer doesn't upgrade client lib, using NamespacedName would still work, it just won't be able to use multicluster service. If they upgrade client lib, they should change the type to PeerService, which kind of change happens in many libraries. |
9e25a17
to
ec6b127
Compare
/test-all /test-multicluster-e2e |
Needs to resolve the conflicts and update the PR title and description as they are stale. Could you squash the commits as well? Otherwise the automatic generated commit would include some historical information about toMulticlusterServices. |
Signed-off-by: Dyanngg <[email protected]> Change toMulticlusterService into scope field in toServices Signed-off-by: Dyanngg <[email protected]> Update mc manifests Signed-off-by: graysonwu <[email protected]>
ec6b127
to
0588522
Compare
scope
field for toServices
in Antrea-native policies
/test-all /test-multicluster-e2e |
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.
LGTM
…ntrea-io#4397) Adds a scope field for toServices feature in Antrea-native policy egress rules. When scope is set to ClusterSet, users can simply provide the name and Namespace of the exported Service, and Antrea will match rule with egress traffic intended for backends of the exported Service across all clusters in the ClusterSet. It is equivalent to putting the imported Service name (antrea-mc- [svcName]) in toServices field without setting scope. Signed-off-by: Dyanngg <[email protected]>
Adds a
scope
field fortoServices
feature in Antrea-native policyegress rules. When
scope
is set toClusterSet
, users can simplyprovide the name and Namespace of the exported Service, and
Antrea will match rule with egress traffic intended for backends of
the exported Service across all clusters in the ClusterSet.
It is equivalent to putting the imported Service name (antrea-mc-
[svcName]) in
toServices
field without settingscope
.Signed-off-by: Dyanngg [email protected]