Added functions for building infra in AWS

[josh-ferrell]

What type of PR is this?
/kind feature

What this PR does / why we need it:
Add some basic CRUD functions for VPCs, subnets, NatGW, IGW, route tables, routes and peering connections to be used by the e2e test suite for building out infrastructure prior to test.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #3235

Special notes for your reviewer:

Checklist:

• squashed commits
• includes documentation
• adds unit tests
• adds or updates e2e tests

Release note:

Added AWS EC2 Service functions for use by e2e tests.

[k8s-ci-robot]

@josh-ferrell: This issue is currently awaiting triage.

If CAPA/CAPI contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[k8s-ci-robot]

Hi @josh-ferrell. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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.

[Ankitasw]

Hey @josh-ferrell, Thanks for the PR.
Are we planning to have getters for all the above mentioned resources as well, as I see them only for subnets and NATGateways?

[josh-ferrell]

@Ankitasw I have them in there for VPC, Subnet, NAT GW, IGW and route tables. I can add GET for peering connections but I'm not sure about individual routes. If so I can add that as well.

[Ankitasw]

@josh-ferrell Hey thanks for pointing out, I think I missed checking NAT gateways and route table thats why asked. I don't think we need for peering connections and individual routes.
/ok-to-test

[josh-ferrell]

/retest-required

[Ankitasw]

@josh-ferrell I think you need to run make lint locally to check and fix lint errors which are failing here.

[josh-ferrell]

Thanks @Ankitasw I think that should take care of it.

[sedefsavas]

We add CCM tags automatically to unmanaged Subnets, in case want to make this more similar. Not required for this PR. Just FYI.

In summary, to identify a cluster's subnets, CCM looks for the following tags:​

• kubernetes.io/cluster/YOUR-CLUSTER-NAME=shared/owned (shared value allows more than one cluster to use the subnet)​

• kubernetes.io/role/elb (for public subnet)​

• kubernetes.io/role/internal-elb (for private subnet)

[sedefsavas]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sedefsavas

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

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

[Ankitasw]

/lgtm