-
Story
-
Resolution: Done
-
Critical
-
None
-
None
-
2
-
True
-
False
-
HAC Console Sprint 244
User story:
So that I can ensure each machine pool has the correct security group, as a user, I want to see the AWS security group(s) attached to a given machine pool (no edit)
Acceptance criteria:
- When viewing an existing machine pool for ROSA classic, OSD AWS BYO-VPC clusters, I can see a list of applied security groups
- For ROSA classic clusters, the SG names are seen
- For OSD clusters, the SG Ids are seen (This will be fixed in a follow-up task, to also show the names when they are defined)
Mockups:
TBD - see PD-1622
The initial idea is to add the information in the expanded section for a machine pool where the subnet, labels, and taints information is located.
Current part of the application
---------------------------------------------------------------------------------------------------------------------------
Implementation and technical notes
1. Initially this only applies to machine pools for ROSA classic, OSD AWS BYO-VPC clusters. Note that ROSA HCP node pools are not included in this story.
2. There may be up to 15 AWS security groups per machine pool. Each machine pool may have a unique set of security groups. (actual number TBD)
3. The AWS security groups will need to be added to this api endpoint
GET /api/clusters_mgmt/v1/clusters/<cluster_id>/machine_pools
- is cloned by
-
OCMUI-951 [OCM UI] Add support for custom security group Day 2 (cluster level) - View only
- Closed
-
OCMUI-949 [OCM UI] Add support for custom security group Day 2 non-STS - View only
- Closed
- is depended on by
-
PD-1622 [ROSA] Add support for custom security group Day 2 - View only
- Closed
- mentioned on