User Story:

As a (user persona), I want my pods workloads to be able to access EC2 Metadata Endpoint over IPv6 (i.e. fd00:ec2::254) by default if cluster infra has IPv6 enabled.

As of now, CAPA only enables IPv4 endpoint. Thus, if a single-stack IPv6 pod needs to access EC2 Metadata Endpoint (i.e. fd00:ec2::254), the request will timeout.

Acceptance Criteria:

Description of criteria:

• EC2 instance metadata option should have http-protocol-ipv6 set to enabled to allow IPv6 metadata endpoint

(optional) Out of Scope:

Detail about what is specifically not being delivered in the story

Engineering Details:

• Block code that modify instance metadata option: https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/dd099ec02cf68ca86ac30317081eddca9415e673/pkg/cloud/services/ec2/instances.go#L1075 
• The logic seems to require a new API field.

This requires/does not require a design proposal.
This requires/does not require a feature gate.