-
Notifications
You must be signed in to change notification settings - Fork 374
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
Document encap mode installation for EKS #2929
Conversation
21c7615
to
748cf22
Compare
Codecov Report
@@ Coverage Diff @@
## main #2929 +/- ##
===========================================
- Coverage 61.59% 40.59% -21.00%
===========================================
Files 283 158 -125
Lines 23644 19950 -3694
===========================================
- Hits 14563 8099 -6464
- Misses 7512 11080 +3568
+ Partials 1569 771 -798
Flags with carried forward coverage won't be shown. Click here to find out more.
|
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.
thanks for validating this, it will be very useful to have that as a reference
do you want to also mention
- the advantages of using encap mode (more Pods per Node, encryption)
- what won't work anymore, notably aggregation
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 advantages of using encap mode (more Pods per Node, encryption)
Makes sense. Add some description in eks-installation.md.
- what won't work anymore, notably aggregation
I found aggregation is working! Might be some changes in EKS.
I think aggregation for Antrea APIs work fine, but I'm not sure how aggregation to a regular Pod (not hostNetwork) can work. Did you check with the metrics server? What's the packet path in that case? |
Ah, you must be right. Let me check, and I can add that if it does not work. Do you have any other issues in mind? |
@jianjuns you may want to test, but I think the built-in apiserver proxy doesn't work either because it relies on the apiserver being able to connect direcly to Pods: https://kubernetes.io/docs/tasks/access-application-cluster/access-cluster/#manually-constructing-apiserver-proxy-urls. So trying to use the proxy to connect to a Service or Pod should fail. I can't think of anything else. |
@antoninbas : added description about the control plane -> Pod connection issue. |
docs/eks-installation.md
Outdated
|
||
In `encap` mode, Antrea acts as the primary CNI of an EKS cluster, and | ||
implements all Pod networking functionalities, including IPAM and routing across | ||
Nodes. The major benefit of Antrea as the primary CNI is that - it can get rid |
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 don't think you need the "-" here
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 it.
docs/eks-installation.md
Outdated
Nodes. The major benefit of Antrea as the primary CNI is that - it can get rid | ||
of the Pods per Node limits with Amazon VPC CNI. For example, the default mode | ||
of VPC CNI allocates a secondary IP for each Pod, and the maximum number of Pods | ||
can be created on a Node is decided by the on the maximum number of elastic |
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.
can be created on a Node is decided by the on the maximum number of elastic | |
that can be created on a Node is decided by the maximum number of elastic |
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.
Thanks!
docs/eks-installation.md
Outdated
network interfaces and secondary IPs per interface that can be attached to an | ||
EC2 instance type. When Antrea is the primary CNI, Pods are connected to the | ||
Antrea overlay network and Pod IPs are allocated from the private CIDRs | ||
configured for an EKS cluster, and so number of Pods per Node is no longer |
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 number of Pods per Node
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.
docs/eks-installation.md
Outdated
EC2 instance type. When Antrea is the primary CNI, Pods are connected to the | ||
Antrea overlay network and Pod IPs are allocated from the private CIDRs | ||
configured for an EKS cluster, and so number of Pods per Node is no longer | ||
limited by number of secondary IPs per instance. |
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 number
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.
docs/eks-installation.md
Outdated
configured for an EKS cluster, and so number of Pods per Node is no longer | ||
limited by number of secondary IPs per instance. | ||
|
||
Note: as a general limitation in EKS's custom CNI support, Antrea cannot be |
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.
as a general limitation when using custom CNIs with EKS, Antrea...
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.
docs/eks-installation.md
Outdated
Note: as a general limitation in EKS's custom CNI support, Antrea cannot be | ||
installed to the EKS control plane Nodes. As a result, EKS control plane | ||
cannot initiate a connection to a Pod in Antrea overlay network, when Antrea | ||
runs in `encap` mode, and so applications that require the control plane to Pod |
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 require control plane to Pod connections
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.
/skip-all |
c0c0af4
to
1ebe9d9
Compare
Signed-off-by: Jianjun Shen <[email protected]>
/skip-all |
Signed-off-by: Jianjun Shen [email protected]
Closes #867