Auto-sync: update nexus workspace
This commit is contained in:
39
wiki/concepts/IPv6-in-EKS.md
Normal file
39
wiki/concepts/IPv6-in-EKS.md
Normal file
@@ -0,0 +1,39 @@
|
||||
---
|
||||
title: "IPv6 in EKS"
|
||||
type: concept
|
||||
tags:
|
||||
- AWS
|
||||
- EKS
|
||||
- IPv6
|
||||
- Networking
|
||||
- IP-Address-Exhaustion
|
||||
sources:
|
||||
- ctp-topic-64-scaling-out-with-amazon-eks
|
||||
last_updated: 2026-04-28
|
||||
---
|
||||
|
||||
## Definition
|
||||
IPv6-in-EKS 是 Amazon EKS 集群解决 IP 地址耗尽(IP Exhaustion)问题的网络架构方案,通过部署 IPv6 或双栈(Dual-Stack)VPC,实现大规模容器工作负载的 IP 地址可持续供给。
|
||||
|
||||
## Problem Statement
|
||||
- 每个 EKS 节点上的 ENI(Elastic Network Interface)附带可分配的 IP 地址数量有限
|
||||
- VPC CIDR 块大小固定,Pod 数量增长导致可用 IP 耗尽
|
||||
- 自定义网络(Custom Networking)和 Prefix Delegation 可缓解但不能根本解决
|
||||
|
||||
## Solution: IPv6 Dual-Stack VPC
|
||||
- **双栈架构**:VPC 同时支持 IPv4 和 IPv6 地址
|
||||
- **节点双协议栈**:EKS 节点同时持有 IPv4 和 IPv6 地址
|
||||
- **Pod 仅 IPv6**:Pod 仅分配 IPv6 地址(节省 IPv4 空间)
|
||||
- **NAT 映射**:IPv6 Pod 与 IPv4 目标通信时,通过双层 NAT 映射转换
|
||||
|
||||
## Alternative: Carrier-Grade NAT (CGNAT)
|
||||
- 如无法迁移至 IPv6,可使用 CGNAT 方案
|
||||
- 通过自定义网络 + NAT 网关聚合多个 Pod 的出站流量
|
||||
|
||||
## Benefits
|
||||
- IP 地址空间近乎无限(解决耗尽问题)
|
||||
- 简化网络配置(无需管理大量 IPv4 地址)
|
||||
- 符合云原生网络发展趋势
|
||||
|
||||
## Sources
|
||||
- [[ctp-topic-64-scaling-out-with-amazon-eks]]
|
||||
Reference in New Issue
Block a user