Egress IP support for both Dual Stack IPv4 and IPv6

1. Proposed title of this feature request

Egress IP support for both Dual Stack IPv4 and IPv6

2. What is the problem that your customer is facing?

The customer needs IPs for certain projects that make message calls to other agencies and vendors. These IPs are used as part of their firewall rules at the enterprise level.

In a dual-stack FIPS-enabled cluster, customers wanted to configure IPv4 and IPv6 Egress IPs for a project. The examples in the documentation only reference IPv4 and they did not find any example of how they can configure  IPv6 Egress IPs against a project/namespace. 

Already advised that they can use Egress Routers for this use-case but that is also not a valid solution as per the below response:
They have numerous teams that send messages out to services outside their network and the firewall rules are handled by their network team. There are also notes about not creating too many Egress Routers. They have upwards of 15 teams that will need to send messages to external sources outsider their network and it will not be feasible for their Networking team to handles those firewall rules.
3. What is the nature and description of the request?

The customer is faced with a mandatory upgrade of their infrastructure to IPv6 by the Office of Management and Budget (OMB) Memorandum M-21-7 for the deployment and use of IPv6. This came out in 2020

4. What are your expectations for this feature //Please add any requirements you may have so that we are able to deliver what you need

Allow Egress IPs to be configured for a namespace that accepts both IPv4 and IPv6 addresses. 

5. Why does the customer need this? (List the business requirements here)

IPv6 is a Federal Mandate; Office of Management and Budget (OMB) Memorandum M-21-7 for the deployment and use of IPv6 

6. What is the business impact, if any, if this request will not be made available? Other

Cloud container offerings would be evaluated. ex: "EKS Anywhere"