<p>I have 3 node group t3a.micro and I installed ebs csi provider and storage-class.</p>
<p>I want deploy statefulset on mysql
this is my manifest</p>
<pre><code>apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: mysql-statefulset
spec:
  serviceName: mysql-service
  replicas: 1
  selector:
    matchLabels:
      app: mysql-pod
  template:
    metadata:
      labels:   
        app: mysql-pod
    spec:
      containers:
      - name: mysql
        image: mysql
        ports:
        - containerPort: 3306
        volumeMounts:
        - name: pvc-test
          mountPath: /var/lib/mysql
  volumeClaimTemplates:
  - metadata:
      name: pvc-test
    spec:
      storageClassName: gp2-retain
      accessModes: [ &quot;ReadWriteOnce&quot; ] 
      resources:
        requests:
          storage: 1Gi
</code></pre>
<p>Warning  FailedScheduling  20s (x16 over 20m)  default-scheduler  0/3 nodes are available: 3 Too many pods.</p>

loanshark
<p>As mentioned in <a href="https://stackoverflow.com/questions/64965832/aws-eks-only-2-pod-can-be-launched-too-many-pods-error">AWS EKS - Only 2 pod can be launched - Too many pods error</a></p>
<p>According to <a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-eni.html#AvailableIpPerENI" rel="nofollow noreferrer">https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-eni.html#AvailableIpPerENI</a>, <code>t3a.micro</code> type has</p>
<pre><code>Maximum network interfaces: 2
Private IPv4 addresses per interface: 2 
IPv6 addresses per interface: 2
</code></pre>
<p>But EKS deploys <code>DaemonSets</code> for e.g. CoreDNS and kube-proxy, so some IP addresses <strong>on each node</strong> is already allocated.</p>
<p>Possible fix is just upgrade your instance to be a more capable type.</p>
