Files
kubernetes/staging
Paul Michali 3d8f96f881 IPv6 support for ChooseHostInterface (part 3 of 3)
This is the final commit, which is based on top of PR 46044 and 46138, and provides
support for Ipv6 for the ChooseHostInterface() and ChooseBindAddress() functions.
The commit includes the following...

- Parses default routes from /proc/net/ipv6_route file.
- Collected IPv6 routes are added to the Ipv4 routes collected.
- ChooseHostInteface semantics remain the same:
    * If no Ipv4 route file, the system interfaces will be checked for a global IP.
    * Otherwise, default routes will be used to find a global IP.
    * If there is a failure getting IP from default routes, an error is reported.
    * Although IPv6 routes are also used, IPv4 routes have precedence.
- Any failure getting IPv6 routes is ignored, and will proceed with IPv4 routes.
- Scans all IPv4 routes looking for interfaces with global IP, before looking at
  IPv6 routes.
- Increased code coverage to 90.2%, covering all new and modified code (except for
  the top level API functions, which would need to be checked with integration/e2e
  tests.

This would complete IPv6 support in this area of the code.

Updated to rebased for changes from 46138/46044, and based on review comments.
2017-07-18 21:07:14 +00:00
..
2017-04-19 15:58:09 -04:00

This directory is the staging area for packages that have been split to their own repository. The content here will be periodically published to respective top-level k8s.io repositories.

Most code in the staging/ directory is authoritative, i.e. the only copy of the code. You can directly modify such code. However the packages in staging/src/k8s.io/client-go/pkg are copied from pkg/. If you modify the original code in pkg/, you need to run hack/godep-restore.sh from the k8s root directory, followed by hack/update-staging-client-go.sh. We are working towards making all code in staging/ authoritative.

The vendor/k8s.io directory contains symlinks pointing to this staging area, so to use a package in the staging area, you can import it as k8s.io/<package-name>, as if the package were vendored. Packages will be vendored from k8s.io/<package-name> for real after the test matrix is converted to vendor k8s components.