Previously, default NooBaa install created unrestricted AWS security groups during deployment. With this update, support for controlling LoadBalancer source subnet is added.
Descriptionetsmith@redhat.com
2021-11-18 16:38:21 UTC
Created attachment 1842613[details]
aws sg screenshot
Description of problem (please be detailed as possible and provide log
snippests):
Default OCS/ODF Operator install creates AWS SGs with 0.0.0.0/0 inbound rules.
Version of all relevant components (if applicable):
OCP 4.8.18
OCS 4.8.2
Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
No, AWS SG rules can be edited after the fact.
Is there any workaround available to the best of your knowledge?
Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
1
Can this issue reproducible?
Yes
Can this issue reproduce from the UI?
Yes
If this is a regression, please provide more details to justify this:
Steps to Reproduce:
1. Install OCS/ODF 4.8 w/ Noobaa
2. AWS SG gets created w/ wide open rules
3.
Actual results:
AWS SG gets created w/ wide open rules
Expected results:
AWS SG gets created w/ rules locked down to VPC CIDR (at least)
Additional info:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Red Hat OpenShift Data Foundation 4.12.0 enhancement and bug fix update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2023:0551
Comment 19Red Hat Bugzilla
2023-12-08 04:26:45 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Created attachment 1842613 [details] aws sg screenshot Description of problem (please be detailed as possible and provide log snippests): Default OCS/ODF Operator install creates AWS SGs with 0.0.0.0/0 inbound rules. Version of all relevant components (if applicable): OCP 4.8.18 OCS 4.8.2 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? No, AWS SG rules can be edited after the fact. Is there any workaround available to the best of your knowledge? Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? 1 Can this issue reproducible? Yes Can this issue reproduce from the UI? Yes If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. Install OCS/ODF 4.8 w/ Noobaa 2. AWS SG gets created w/ wide open rules 3. Actual results: AWS SG gets created w/ wide open rules Expected results: AWS SG gets created w/ rules locked down to VPC CIDR (at least) Additional info: