-
Task
-
Resolution: Done
-
Critical
-
None
-
None
-
None
-
False
-
None
-
False
-
No
-
MGDSRVS-52 - Ensure our service is profitable or has a profitability path
-
---
-
---
-
MK - Sprint 225, MK - Sprint 226, MK - Sprint 227, MK - Sprint 228
WHAT
Move broker nodes from m5.2xlarge to r5.xlarge nodes
WHY
To reduce AWS costs
HOW
As part of profile segregation, the broker worker nodes need to be moved to different machine pools, r5.xlarge should be used as a machine class.
DONE
when production deployment is completed
Guidelines
The following steps should be adhered to:
- Required tests should be put in place - unit, integration, manual test cases (if necessary)
- CI and all relevant tests passing
- Changes have been verified by one additional reviewer against:
- each required environment
- each supported upgrade path
- If the changes could have an impact on the clients (either UI or CLI), a JIRA should be created for making the required changes on the client side and acknowledged by one of the client side team members. PR has been merged
- is blocked by
-
MGDSTRM-9799 Add fleetshard handling for r5.xlarge
- Closed
-
MGDSTRM-9802 Move the broker nodes r5.xlarge
- Closed
- is cloned by
-
MGDSTRM-9799 Add fleetshard handling for r5.xlarge
- Closed
-
MGDSTRM-9802 Move the broker nodes r5.xlarge
- Closed
- is related to
-
MGDSTRM-9524 Investigate changing the worker node type in KFM
- Closed