-
Epic
-
Resolution: Done
-
Normal
-
None
-
None
-
Add Support for configuring day 2 security group
-
False
-
None
-
False
-
Not Selected
-
To Do
-
XCMSTRAT-41 - ROSA: Additional Security Group(s) for Optional Machine Pools (Day-2)
-
-
0% To Do, 0% In Progress, 100% Done
Epic Goal
- Improve ROSA retention by providing an ability to add additional machine pools with additional Security Group IDs to existing clusters
- Support for ROSA Classic and OSD on AWS using OCP 4.11 and above.
Why is this important?
This feature strengthens both security and AWS integration themes of ROSA service. Developers deploying workloads in ROSA service often need to connect their workloads running inside OCP to other AWS Services or applications running in other VPCs. This feature will allow cluster administrators to assign optional additional Security Groups to control plane nodes, infra nodes, and all the worker nodes of machine pools (at machine pool granularity).
Scenarios
- ...
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- …
Open questions::
- …
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
- DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
- DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Downstream documentation merged: <link to meaningful PR>