1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
2
It is possible to have a node that has 2 ENIs without having to manually configure it in Launch templates. Amazon EC2 provides a wide selection of instance types for worker nodes. Each instance type offers its own maximum number of ENI. For example, t3.micro has 2 maximum network interfaces. Refer to doc for a table that lists the maximum number of network interfaces per instance type.
beantwortet vor einem Jahr
Relevanter Inhalt
AWS OFFICIALAktualisiert vor 8 Monaten- AWS OFFICIALAktualisiert vor 6 Monaten
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
I see that document , my main question is how to setup node to have 2 network interface in initial setup , if I use create node group wizard you choose instance witch support 2 and more interface , but you can't select number of interface for deploy of those nodes.
Nenad, if you are using the Amazon VPC CNI then it will proactively manage the ENIs actually used. With the same numbers as the doc Olawale noted, this file https://github.com/awslabs/amazon-eks-ami/blob/master/files/eni-max-pods.txt describes the maximum number of pods per node. What is your use case for wanting to manage the number of ENIs yourself instead of letting the
aws-nodeagent (DaemonSet pod for Amazon VPC CNI) manage them for you?You could alternatively use self-managed nodes if that is what you really need/want.
Hi Brad ,thx for answers. The thing is a app witch we plan to deploy on EKS need to received traffic A to one NIC and traffic B on another NIC (this is a requirement) , trust me it would be easier for me to use EKS CNI and setup two NICs on a pod. It is possibility that I will need to deploy the app with hostNetwork: true so app pickup host network.