enable ipv6 forwarding on instances

[aojea]

We need to enable ipv6 forwarding on instance in order to support ipv6 k8s clusters.

[aojea]

/assign @detiber
/cc @dims

[aojea]

I want to check first if something else is missing
/hold

[dims]

@aojea how's this going? need some help?

[aojea]

@aojea how's this going? need some help?

I'm able to deploy the network infra with my PR to the cluster-api-provider-aws, but I'm trying to fix the panics with the conversions.

Although the subnets and VPC are created, I can't progress because I can't use the cloudformation template in my account :/ , need to check if I can get some way to overcome that.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[detiber]

/lifecycle frozen

[aojea]

/hold cancel
I've documented how to deploy k8s ipv6 clusters in AWS here (still missing the aws-cloud-provider integration) https://github.com/aojea/k8s-aws-ipv6

we need to enable this kernel parameters to be able to use these images
@justinsb @dims @detiber @andrewsykim

[dims]

cc @jayunit100 @sedefsavas

[dims]

/approve
/lgtm

[aojea]

/assign @detiber

[detiber]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aojea, detiber, dims

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:

• images/capi/OWNERS [detiber]

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