Update kube-router to 1.6

[aauren]

This PR, updates kube-router to the latest stable 1.X release (1.6.0). It is primarily a dependency update release and has been released for several months. If this goes well, the next step would be to upgrade to kube-router 2.X which is the most recent stable release, but comes with a few breaking changes.

I have also removed the deprecation notices for kube-router since I'm now committing to maintaining it. I have split out a 3rd commit that removes the deprecation notices for kube-router from the kops release notes. However, I left it as a separate commit, because I'm not sure if the project considers release notes like that immutable. Let me know the best way to proceed, and I can modify the PR accordingly.

After upgrading it, I have tested it against my own kops cluster and I have also run the kubetest2 e2e tests. kube-router's test results against the sig-network conformance tests are the same both before and after the upgrade. It currently fails 9 of the sig-network conformance tests. This is something that I was already interested in fixing upstream, so I'll work on that on the 2.X release line over the course of the next several months.

FYI @hakman

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: aauren / name: Aaron U'Ren (36ad005, 6903c6c, f31ca6f)

[k8s-ci-robot]

Welcome @aauren!

It looks like this is your first PR to kubernetes/kops 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/kops has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @aauren. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[hakman]

/ok-to-test

[hakman]

Thanks @aauren, much appreciated! :)
/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hakman

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [hakman]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment