Add ipv6 support for EKS

[Skarlso]

What type of PR is this?

/kind feature

What this PR does / why we need it:

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

We are aiming to do as less as possible so the PR doesn't get too much bloated.

Special notes for your reviewer:

This will be Part 1 for IPv6 support. What does Part 1 contain you might ask?

• create an ipv6 cluster
• refactor the code to offer both options without needing to use a lot of ifs
• validations for things that ipv6 doesn't support and capa wouldn't support in the beginning

E2E test run for EKS cluster:

Ran 1 of 3 Specs in 1488.316 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 2 Skipped

Checklist:

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

Release Notes:

To enable permissions to use ipv6 networking, clusterawsadm needs to be executed with additional prerequisites.
Please refer to the prerequisites documentation for details on what to set in the clusterawsadm config file.

[k8s-ci-robot]

@Skarlso: 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 @Skarlso. 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.

[Skarlso]

/assign Skarlso
/assign nikimanoledaki

[k8s-ci-robot]

@Skarlso: GitHub didn't allow me to assign the following users: nikimanoledaki.

Note that only kubernetes-sigs members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign Skarlso
/assign nikimanoledaki

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.

[richardcase]

/ok-to-test

[Skarlso]

/test pull-cluster-api-provider-aws-e2e
/test pull-cluster-api-provider-aws-e2e-clusterclass
/test pull-cluster-api-provider-aws-e2e-eks

[richardcase]

All tests passing so:

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: richardcase

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

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