-
Story
-
Resolution: Duplicate
-
Normal
-
ACM 2.12.0
-
None
Value Statement
To begin determining what the appropriate sizes are for the hub size scaling configurations (i.e default, small, medium, large, & xlarge), we need to determine the different variables that impact the <squad> component based on the different size cluster environments.
The default values can be configured as the current values that are being within the current release version. Each squad will be required to add a new column or replace the sample column with a field that impacts their component (i.e # of resources, # of managed clusters, etc).
Link to Docs:
Definition of Done for Engineering Story Owner (Checklist)
- [ ] Doc is updated to include hub sizing estimates.
Development Complete
- The code is complete.
- Functionality is working.
- Any required downstream Docker file changes are made.
Tests Automated
- [ ] Unit/function tests have been automated and incorporated into the
build. - [ ] 100% automated unit/function test coverage for new or changed APIs.
Secure Design
- [ ] Security has been assessed and incorporated into your threat model.
Multidisciplinary Teams Readiness
- [ ] Create an informative documentation issue using the Customer
Portal Doc template that you can access from [The Playbook](
and ensure doc acceptance criteria is met.
- Call out this sentence as it's own action:
- [ ] Link the development issue to the doc issue.
Support Readiness
- [ ] The must-gather script has been updated.
- clones
-
ACM-13504 Update document with sizing details of <Cluster Lifecycle> components
- Closed