Add IPv6 address support for pods - does NOT include services

[tgraf]

This allows a container to have an IPv6 address only and extracts the address via nsenter and iproute2 or the docker client directly. An IPv6 address is now correctly reported when describing a pod.

@thockin @kubernetes/sig-network

---

This change is

[k8s-bot]

Can one of the admins verify that this patch is reasonable to test? (reply "ok to test", or if you trust the user, reply "add to whitelist")

This message may repeat a few times in short succession due to jenkinsci/ghprb-plugin#292. Sorry.

Otherwise, if this message is too spammy, please complain to ixdy.

[k8s-bot]

Can one of the admins verify that this patch is reasonable to test? (reply "ok to test", or if you trust the user, reply "add to whitelist")

This message may repeat a few times in short succession due to jenkinsci/ghprb-plugin#292. Sorry.

Otherwise, if this message is too spammy, please complain to ixdy.

[k8s-bot]

Can one of the admins verify that this patch is reasonable to test? (reply "ok to test", or if you trust the user, reply "add to whitelist")

This message may repeat a few times in short succession due to jenkinsci/ghprb-plugin#292. Sorry.

Otherwise, if this message is too spammy, please complain to ixdy.

[lxpollitt]

cc @tomdee @caseydavenport

[vishh]

ok to test

[marun]

#23317 is likely relevant

[tgraf]

This and #23317 are coming out of the same effort. We are working together and have tested the changes in combination as well. Both changes are needed separately.

[bgrant0607]

Ref #1443

[thockin]

add to whitelist

[thockin]

re-titling for release note

[thockin]

@k8s-bot test this: github issue #IGNORE

[thockin]

@k8s-bot test this: issue #25392

[k8s-github-robot]

@k8s-bot test this [submit-queue is verifying that this PR is safe to merge]

[k8s-bot]

GCE e2e build/test passed for commit 90623d9.

• Build Log
• Test Artifacts
• Internal Jenkins Results

[k8s-github-robot]

Automatic merge from submit-queue

[danehans]

@tgraf I'm trying to test the functionality of this patch. I updated my docker daemon to run ipv6 by adding the following:

--ipv6 --fixed-cidr-v6="2001:db8:1::/64"

I have verified that the docker daemon can run an Ubuntu container and properly configure an IPv6 address for eth0. However, when I try to instantiate a k8s pod, it gets assigned an IPv4 address.

I used kubeadm with the weave cni plugin to deploy my k8s cluster. It appears that weave dos not support IPv6. What network plugin did you use to test this patch? Are any changes required other than the 2 dockerd flags?

Client Version: version.Info{Major:"1", Minor:"5", GitVersion:"v1.5.1", GitCommit:"82450d03cb057bab0950214ef122b67c83fb11df", GitTreeState:"clean", BuildDate:"2016-12-14T00:57:05Z", GoVersion:"go1.7.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"5", GitVersion:"v1.5.2", GitCommit:"08e099554f3c31f6e6f07b448ab3ed78d0520507", GitTreeState:"clean", BuildDate:"2017-01-12T04:52:34Z", GoVersion:"go1.7.4", Compiler:"gc", Platform:"linux/amd64"}```

/cc @caboucha @rpothier @asomya

[caseydavenport]

@danehans - Might want to check out Calico, which supports IPv6. It can be configured in the CNI plugin as documented here. I know of at least one other user who is using Calico to do IPv6 for k8s.

[tgraf]

@danehans As @caseydavenport correctly hints, this patch assumes that whatever CNI plugin is configured to do networking will allocate an IPv6 address to the pod. It will work with any plugin that supports IPv6 allocation.

[danehans]

@caseydavenport @tgraf thanks for the insight. I'll test with Calico.

[akhildangore]

Hello all,

Does the Kubernestes supports IPv6 address to the pods and services ?

if yes, how to enable IPv6 address while creating pods?

[gino9705]

Hello, all,
Could anyone help us to know how we could enable IPv6 address to the pods and services ??

[danehans]

We are shooting for official support in the 1.8/1.9 release timeframe. A considerable amount of required IPv6 code has merged, so feel free to experiment.

CNI 0.6.0 adds IPv6 support. You can test IPv6 pods with a CNI 0.6.0 plugin. Here is a brief list of steps for testing:

1. SSH to your test node(s) that run kubelet.
2. Download and untar the 0.6.0 plugins.
3. Copy the bridge and host-local plugin bins to /opt/cni/bin
4. Copy the following CNI conf file to /etc/cni/net.d/mynet.conf. Note: The bridge plugin does not support routing between nodes. To provide inter-node pod networking, you must manually add static routes on nodes or provide another mechanism for dynamic routing.

{
  "cniVersion": "0.3.0",
  "name": "mynet",
  "type": "bridge",
  "bridge": "cbr0",
  "isDefaultGateway": true,
  "ipMasq": false,
  "ipam": {
    "type": "host-local",
    "ranges": [
      {
        "subnet": "fd00:101::0/64",
        "gateway": "fd00:101::1"
      }
    ]
  }
}

4. /opt/cni/bin and /etc/cni/net.d/mynet.conf are the default locations kubelet looks for CNI plugins and configuration files. Verify that kubelet --cni-bin-dir and --cni-conf-dir configuration flags are either unset or set to: --cni-bin-dir /opt/cni/bin --cni-conf-dir /etc/cni/net.d
5. Start/restart kubelet
6. Create a pod and test IPv6 network connectivity.

The following PRs need to be merged for supporting the Kubernetes Service resource. Feel free to review and provide feedback:

#48551
#50478

Use the area/ipv6 label in PRs and Issues for tracking purposes.

/cc @leblancd @pmichali @rpothier

[k8s-ci-robot]

@danehans: GitHub didn't allow me to request PR reviews from the following users: leblancd, rpothier.

Note that only kubernetes members can review this PR, and authors cannot review their own PRs.

In response to this:

We are shooting for official support in the 1.8/1.9 release timeframe. A considerable amount of required IPv6 code has merged, so feel free to experiment.

CNI 0.6.0 adds IPv6 support. You can test IPv6 pods with a CNI 0.6.0 plugin. Here is a brief list of steps for testing:

1. SSH to your test node(s) that run kubelet.
2. Download and untar the 0.6.0 plugins.
3. Copy the bridge and host-local plugin bins to /opt/cni/bin
4. Copy the following CNI conf file to /etc/cni/net.d/mynet.conf. Note: The bridge plugin does not support routing between nodes. To provide inter-node pod networking, you must manually add static routes on nodes or provide another mechanism for dynamic routing.

{
 "cniVersion": "0.3.0",
 "name": "mynet",
 "type": "bridge",
 "bridge": "cbr0",
 "isDefaultGateway": true,
 "ipMasq": false,
 "ipam": {
   "type": "host-local",
   "ranges": [
     {
       "subnet": "fd00:101::0/64",
       "gateway": "fd00:101::1"
     }
   ]
 }
}

4. /opt/cni/bin and /etc/cni/net.d/mynet.conf are the default locations kubelet looks for CNI plugins and configuration files. Verify that kubelet --cni-bin-dir and --cni-conf-dir configuration flags are either unset or set to: --cni-bin-dir /opt/cni/bin --cni-conf-dir /etc/cni/net.d
5. Start/restart kubelet
6. Create a pod and test IPv6 network connectivity.

The following PRs need to be merged for supporting the Kubernetes Service resource. Feel free to review and provide feedback:

#48551
#50478

Use the area/ipv6 label in PRs and Issues for tracking purposes.

/cc @leblancd @pmichali @rpothier

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[danehans]

/area ipv6