diff options
| author | Brian Grant <bgrant0607@users.noreply.github.com> | 2017-01-18 13:20:47 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-01-18 13:20:47 -0800 |
| commit | d8e15a451ad38eb6bb64f84787a347723df01e34 (patch) | |
| tree | dfc2e8920f86617252ce06aa58d7f28de4d6301e | |
| parent | 88080fe3f22b6c6eb0b24deff3aa23d3354c87ca (diff) | |
| parent | c5788b76dbe5e8feb8dda83ecc1e1682349005a4 (diff) | |
Merge pull request #271 from zen/networking_docs
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 --> []() |