1. Proposed title of this feature request
Ans: Missing unallocated/unassigned egressip metrics in Prometheus 

2. What is the nature and description of the request?

Ans:  Addition of Prometheus metrics to improve observability and troubleshooting of EgressIP-related operations. Specifically, need metrics that enable better visibility into the allocation, traffic, and health of EgressIP configurations across the cluster.

Requested Metrics:

• Metrics to identify missing, unallocated, or unassigned EgressIPs.

• Metrics showing which pods are attached to specific EgressIPs.

• Metrics capturing total packets and packet drops for traffic flowing through EgressIPs.

• Metrics indicating nodes with stale NAT entries.

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

Ans:  Cu would  like to create an alert with egressIP related prometheus metrics.

4. List any affected packages or components.

Ans:  Applications downtime, as all the traffic going outside of Openshift fails due to this issue.

5. Business Justification:

Customer use EgressIPs for several production applications to be able to scope down firewall rules to just the applications that require it. Currently, there isn't much observability provided to help us monitor the existence and health of these EgressIP objects. 
There is an active bug customer have  identified with OpenShift that results in network disruptions for applications attached to EgressIPs on clusters using OVN Kubernetes.  Adding these metrics would allow customer to historically track which nodes are hosting EgressIPs, identify if there are network disruptions occurring with EgressIP traffic flows, and identify the impacted applications. As customer actively experiencing this bug in their environments, it is something cu like to have monitoring built around to help them identify issues and troubleshoot them in production