Upate Lyft CNI to v0.5.1

[maruina]

This PR:

• Update the Lyft CNI to v0.5.1
• Add a new IAM policy because ec2:DescribeVpcs is required for m5 and c5 instances because the AWS metadata server does not return the secondary CIDR block on these instance types.
• Add the Lyft CNI to the documentation

Marked as WIP because I still need to test this build by spinning up a new cluster, but I'm happy to get any feedback if you something that doesn't look right.
Tested by creating a new cluster and upgrading an existing one.

[k8s-ci-robot]

Hi @maruina. 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.

[rifelpet]

/ok-to-test

[phyllisstein]

Particularly jazzed about the documentation! I might propose adding a note about the creating a VPC in advance and setting spec.networkID. Probably should have been self-evident from the CNI docs, but I wound up struggling to get the sequence straight anyway.

ETA: You're gonna have a bad time, though: the upstream team forgot to build the binaries for the v0.5.0 release 🤦‍♂.

[maruina]

This has been tested in the following scenario:

• updating a cluster running lyft 0.4.0 to 0.5.0
• spinning up a lyft 0.5.0 cluster

I think the only thing missing before merging this is where to store the binaries :)

[maruina]

@phyllisstein I updated the docs, please tell me if it makes more sense

[phyllisstein]

Thanks for indulging my confusion, and thanks again for the extra docs.

[maruina]

The binary has been built by Lyft, so we can review (and hopefully merge) this.

[rifelpet]

Thanks for sticking with it!

/lgtm

[mikesplain]

Thanks @maruina!

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: maruina, mikesplain

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 [mikesplain]

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