-
Notifications
You must be signed in to change notification settings - Fork 368
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 a toggle for Multi-cluster Pod-to-Pod connectivity #4605
Conversation
Codecov Report
@@ Coverage Diff @@
## main #4605 +/- ##
==========================================
+ Coverage 68.67% 69.70% +1.03%
==========================================
Files 400 412 +12
Lines 59450 58332 -1118
==========================================
- Hits 40828 40662 -166
+ Misses 15804 14893 -911
+ Partials 2818 2777 -41
*This pull request uses carry forward flags. Click here to find out more.
|
@hjiajing please fix github check failure. |
259c89b
to
863505f
Compare
@luolanzone Thanks for the reminder. The I think another PR will face the same problem, I'll fix it, too. |
863505f
to
db90739
Compare
docs/multicluster/user-guide.md
Outdated
ConfigMap `antrea-mc-controller-config` of each member cluster like the example | ||
below. Note, **Pod CIDRs must not overlap among clusters to enable cross-cluster | ||
within a ClusterSet. To enable this feature, the cluster's Pod CIDRs must be set | ||
in ConfigMap `antrea-mc-controller-config` of each member cluster and make sure |
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.
Probably use passive voice for both to consistent: "and multicluster.enablePodToPodConnectivity
must be set to true
in the `antrea-agent' configuration"
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.
Changed to passive voice.
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.
Then we should remove "make sure" too.
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.
Removed.
db90739
to
00c9f66
Compare
docs/multicluster/user-guide.md
Outdated
below. Note, **Pod CIDRs must not overlap among clusters to enable cross-cluster | ||
within a ClusterSet. To enable this feature, the cluster's Pod CIDRs must be set | ||
in ConfigMap `antrea-mc-controller-config` of each member cluster and make sure | ||
that `enablePodToPodConnectivity` is set to `true` in antrea-agent ConfigMap. |
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.
that `enablePodToPodConnectivity` is set to `true` in antrea-agent ConfigMap. | |
that `enablePodToPodConnectivity` is set to `true` in ConfigMap `antrea-config`. |
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.
I suggest to use "in the antrea-agent
configuration". I know we usually say ConfigMap for MC Controller configuration in this doc, but I think we usually do not say Antrea ConfigMap for agent/controller configuration in other docs. Technically, we can pass configuration to controllers/agent without a ConfigMap.
If we still want to use "ConfigMap", then we should at least say "ConfigMap in the Antrea deployment manifest" to be clear.
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.
Fixed.
docs/multicluster/user-guide.md
Outdated
antrea-controller.conf: | | ||
featureGates: | ||
... | ||
Multicluster: true | ||
... | ||
multicluster: | ||
enablePodToPodConnectivity: true |
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.
The format is incorrect, please add necessary empty spaces.
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.
Yes, I double-checked then found that once I push code, the IDE will format the Markdown file automatically with a wrong format. I enabled the feature now.
docs/multicluster/user-guide.md
Outdated
ConfigMap `antrea-mc-controller-config` of each member cluster like the example | ||
below. Note, **Pod CIDRs must not overlap among clusters to enable cross-cluster | ||
within a ClusterSet. To enable this feature, the cluster's Pod CIDRs must be set | ||
in ConfigMap `antrea-mc-controller-config` of each member cluster and make sure |
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.
Then we should remove "make sure" too.
docs/multicluster/user-guide.md
Outdated
below. Note, **Pod CIDRs must not overlap among clusters to enable cross-cluster | ||
within a ClusterSet. To enable this feature, the cluster's Pod CIDRs must be set | ||
in ConfigMap `antrea-mc-controller-config` of each member cluster and make sure | ||
that `enablePodToPodConnectivity` is set to `true` in antrea-agent ConfigMap. |
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.
I suggest to use "in the antrea-agent
configuration". I know we usually say ConfigMap for MC Controller configuration in this doc, but I think we usually do not say Antrea ConfigMap for agent/controller configuration in other docs. Technically, we can pass configuration to controllers/agent without a ConfigMap.
If we still want to use "ConfigMap", then we should at least say "ConfigMap in the Antrea deployment manifest" to be clear.
pkg/config/agent/config.go
Outdated
@@ -292,6 +292,9 @@ type MulticlusterConfig struct { | |||
// Enable Multi-cluster NetworkPolicy which allows Antrea-native policy ingress rules to select peers | |||
// from all clusters in a ClusterSet. | |||
EnableStretchedNetworkPolicy bool `yaml:"enableStretchedNetworkPolicy,omitempty"` | |||
// Enable Multi-cluster Pod to Pod Connectivity which allows one Pod access another Pod in other member | |||
// clusters directly. It also requires the Pod CIDRs in Multi-cluster configuration. |
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.
"This feature also requires Pod CIDRs to be provided in the Multi-cluster Controller configuration"
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.
Done.
00c9f66
to
85d5853
Compare
@hjiajing please help to resolve the manifest conflicts. thanks. |
below. Note, **Pod CIDRs must not overlap among clusters to enable cross-cluster | ||
within a ClusterSet. To enable this feature, the cluster's Pod CIDRs must be set | ||
in ConfigMap `antrea-mc-controller-config` of each member cluster and | ||
`multicluster.enablePodToPodConnectivity` must be set to `true` in the `antrea-agent` |
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.
I suppose we should highlight this toggle is introduced from v1.11? @jianjuns any suggestion?
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.
I feel it is not important. But if we want, no harm to add the information either.
85d5853
to
ee18aa2
Compare
@luolanzone Thanks for the reminder, regenerated the manifest and resolved the conflict now. |
/test-e2e |
@hjiajing : some tests have been pending for long, and some (e.g. multicluster-e2e) are not shown on the PR. Please re-push the commit, and make sure the required tests are passed. |
Signed-off-by: hujiajing <hjiajing@vmware.com>
ee18aa2
to
7cf1a3f
Compare
@jianjuns Thanks for the reminder, pe-pushed now. |
/test-e2e |
/test-all |
/test-e2e |
/test-multicluster-e2e |
Add a toggle for Multi-cluster Pod-to-Pod connectivity in antrea-agent configuration. The Pod-to-Pod connectivity feature will be enabled when the toggle is set true and Pod CIDRs are provided in the Antrea Multi-cluster configuration.