1. Proposed title of this feature request: SG- ingress rules with Rules 0.0.0.0/0 ingress

2. What is the nature and description of the request?
In their AWS environment, customer has a security control that enforce security standard. In the case the action or the configuration is not compliant, there is a auto remediation that is applied.

When the platform wants to create an ingress rule passing through the load balancer, an SG is created with the the default source 0.0.0.0/0. This is not allowed in customer's environment and cx saw the remediation and error in the cloudtrail. Customer wants to bypass the internal processes to have a exception to remove auto-remediation on this rule.

3. Why does the customer need this? (List the business requirements here)
Customer's internal cluster is only intended to expose application internally, it would be good to have a way to provide at the installation default cidr for ingress that corresponding to their network, not allow any source.

4. List any affected packages or components.
This causes the ingress cluster operator to go into degraded state in their ROSA HCP cluster lot of times. This is putting production deadlines at risk.

After discussing with MOBB and SRE on slack thread: https://redhat-internal.slack.com/archives/CCX9DB894/p1754529908362119 , opening this RFE ticket to find a way around this for customer.