diff options
| author | Tomasz 'Zen' Napierala <tomasz@napierala.org> | 2017-01-16 16:45:09 +0100 |
|---|---|---|
| committer | Tomasz 'Zen' Napierala <tomasz@napierala.org> | 2017-01-16 16:45:09 +0100 |
| commit | c5788b76dbe5e8feb8dda83ecc1e1682349005a4 (patch) | |
| tree | fed4c0befc51657199252e4975ad7e125cc162ea | |
| parent | 717088c7fe52cc368e0a53c1289db5f3690a29ec (diff) | |
Updated ipv6 support docs
| -rw-r--r-- | contributors/design-proposals/networking.md | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/contributors/design-proposals/networking.md b/contributors/design-proposals/networking.md index 9c0bbec9..df8c8f82 100644 --- a/contributors/design-proposals/networking.md +++ b/contributors/design-proposals/networking.md @@ -180,10 +180,11 @@ and the network plugin architecture Kubernetes uses needs to allow returning IPv6 addresses too [CNI issue #245](https://github.com/containernetworking/cni/issues/245). Kubernetes code that deals with IP addresses must then be audited and fixed to support both IPv4 and IPv6 addresses and not assume IPv4. -Additionally, direct ipv6 assignment to instances doesn't appear to be supported -by major cloud providers (e.g., AWS EC2, GCE) yet. We'd happily take pull -requests from people running Kubernetes on bare metal, though. :-) - +AWS started rolling out basic +[ipv6 support](https://aws.amazon.com/about-aws/whats-new/2016/12/announcing-internet-protocol-version-6-support-for-ec2-instances-in-amazon-virtual-private-cloud/), +but direct ipv6 assignment to instances doesn't appear to be supported by other +major cloud providers (e.g. GCE) yet. We'd happily take pull requests from people +running Kubernetes on bare metal, though. :-) <!-- BEGIN MUNGE: GENERATED_ANALYTICS --> []() |