Feature Overview (aka. Goal Summary)  

An elevator pitch (value statement) that describes the Feature in a clear, concise way.  Complete during New status.

Customer has a Openshift 4.12 cluster deployed on Google Cloud using IPI method.

For instance, Customer have the default IngressController exposed using a LoadBalancer service and Openshift deploys in Google Cloud the infrastructure need for that: a TCP internal load balancer and a firewall.

oc get svc -n openshift-ingress
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
router-default LoadBalancer 172.30.147.102 10.64.217.208 80:30228/TCP,443:31171/TCP 495d

The problem I see is that the firewall allows by default traffic from anywhere i.e 0.0.0.0/0 (see screenshot). I already know that firewall rule can be restricted if Service is annotated with service.beta.kubernetes.io/load-balancer-source-ranges but some administrators may not know it

I would like to know if can raise a RFE or similar, to restrict a little more firewall rule for Ingress Controller LoadBalancer service because this default current configuration may allow access from external enviroments and losing track of what can access to the Load Balancer

<your text here>

Goals (aka. expected user outcomes)

The observable functionality that the user now has as a result of receiving this feature. Include the anticipated primary user type/persona and which existing features, if any, will be expanded. Complete during New status.

Customer wants that when the loadbalancer service (or any other service is created) it should be restricted by default(now open to outside world) and traffic should be allowed only after explicitly allowing. Let say by annotation or by any other way

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order to be considered complete.  Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc.  Initial completion during Refinement status.

<enter general Feature acceptance here>

Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.

Use Cases (Optional):

Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

<your text here>

Questions to Answer (Optional):

Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

<your text here>

Out of Scope

High-level list of items that are out of scope.  Initial completion during Refinement status.

<your text here>

Background

Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

<your text here>

Customer Considerations

Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

<your text here>

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.

<your text here>

Interoperability Considerations

Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

<your text here>