Update kube-router to v2.1.0

[aauren]

@hakman for review

Changes:

• Bump kube-router version to v2.1.0 from v1.6.0
• Enable hairpin mode for kube-router by default - From the e2e tests this seems to be expected functionality of a CNI
• Add the runtime endpoint into the container so that user's are able to utilize DSR functionality
• Mount /etc/iproute2/rt_tables into the container as well which is used by kube-router to configure source routing for DSR
• Add hostPID: true functionality for DSR
• Add environment var POD_NAME so that user's can easily enable load-balancing mode for kube-router
• Add additional RBAC for the following:
  • leases / services/status - For loadbalancer controller which can be optionally enabled
  • endpointslices - This is needed in kube-router v2.X and on so that kube-router is able to handle dual-stack endpoints

I found that in the current main branch of kops that kube-router's old method of adding instance modify permissions to the nodes no longer works correctly. I believe that this permission should be coming in when kube-router is chosen as the networking provider:

• https://github.com/kubernetes/kops/blob/master/pkg/model/components/addonmanifests/kuberouter/iam.go#L35
• https://github.com/kubernetes/kops/blob/master/pkg/model/iam/iam_builder.go#L1086-L1090

However, this no longer seems to be applying to nodes correctly and when this is missing kube-router is not able to forward pod traffic to other nodes.

After poking around a bit, I also noticed that other CNIs like Calico have special logic in the IAM builder like the following to add similar functionality in the IAM node builder code: https://github.com/kubernetes/kops/blob/master/pkg/model/iam/iam_builder.go#L467-L469

So I added this functionality for kube-router as well and found that it works correctly and enables kube-router to disable the src-dest check in AWS.

Additionally removed all of the skip_regex.go exceptions that were kept for kube-router as with this version update kube-router now passes all of the upstream e2e conformance tests.

[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

[aauren]

I went ahead and re-added the skip regex for the 2 failing kube-router tests TCP close/wait which appears to be flaky as this one isn't failing consistently in my similar test-bed and the kube-proxy URLs one as something appears to have changed in the test package that causes this to fail.

I'll look more into these later, but this should hopefully get it through.

[hakman]

Nice bump. Thanks @aauren!
/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

[k8s-ci-robot]

@aauren: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-kops-e2e-cni-cilium-ipv6	821ab18	link	false	/test pull-kops-e2e-cni-cilium-ipv6
pull-kops-e2e-cni-calico-ipv6	821ab18	link	false	/test pull-kops-e2e-cni-calico-ipv6

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

[hakman]

/test pull-kops-e2e-cni-amazonvpc

[hakman]

/test pull-kops-e2e-k8s-aws-calico