<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>eks - Tag - weichen's note</title><link>https://droyuki.github.io/en/tags/eks/</link><description>eks - Tag - weichen's note</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>droyuki@gmail.com (weichen)</managingEditor><webMaster>droyuki@gmail.com (weichen)</webMaster><lastBuildDate>Sat, 10 Jun 2023 12:06:35 +0800</lastBuildDate><atom:link href="https://droyuki.github.io/en/tags/eks/" rel="self" type="application/rss+xml"/><item><title>Save EKS IP Resources with Pod SNAT</title><link>https://droyuki.github.io/en/2023/06/eks-nodegroup-in-private-snet/</link><pubDate>Sat, 10 Jun 2023 12:06:35 +0800</pubDate><author>weichen</author><guid>https://droyuki.github.io/en/2023/06/eks-nodegroup-in-private-snet/</guid><description>Background Since the company-assigned VPC is an Intranet segment, used for interfacing with the local end, from the organization&amp;rsquo;s perspective, the VPC is not truly &amp;lsquo;Private&amp;rsquo;, therefore the IP quantity is still limited. Following the discovery that EKS Pods occupy ENIs, in order to solve this issue, I added another set of Private IP associated with the VPC, then performed a layer of translation via a Private NAT Gateway. This enables all EKS Pods to communicate with the local network segment through the same Intranet IP, achieving the goal of saving IP resources.</description></item></channel></rss>