-
Feature Request
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
False
-
None
-
False
-
Not Selected
-
-
-
-
Red Hat OpenShift Service on Amazon
- Proposed title of this feature request
- Let Ingresscontroller NLB to have its own security group instead of using backend EC2 instance security group
- What is the nature and description of the request?
- Customer has security mandates for NLBs to have their own security group. NLBs created by Ingress controller use backend worker securitygroup instead creating and using one for NLB. In 4.13 and down, the customer has security group for CLBs. The customer is requesting a similar kind of setup for NLB as well.
- Why does the customer need this? (List the business requirements here)
- Necessary to meet internal security mandates for the customer's use-case.
- List any affected packages or compounds.
- N/A
- duplicates
-
RFE-4812 Security groups for Network Load Balancer
-
- Approved
-
Is the request here to have OpenShift automatically create a security group for the NLB, or to allow the customer to create a security group and link it to the NLB? I want to understand whether OpenShift or the cluster-admin would own the life-cycle of the security group.