-
Spike
-
Resolution: Unresolved
-
Major
-
Global Hub 1.4.0
Value Statement
Save cost - we can install the global hub in the existing ACM hub cluster and do not need to create a new OpenShift cluster for global hub anymore
Definition of Done for Engineering Story Owner (Checklist)
- introduce disableHubSelfManagement field in Global hub CR to control whether we need to deploy global hub agent into the global hub cluster or not. disableHubSelfManagement=false by default
- if disableHubSelfManagement=false, the global hub agent will be deployed in the global hub cluster
- from the global hub dashboard, we can see the local-cluster as a hub cluster which can host some managed clusters.
- Won't impact on the existing features for the regular ACM hub
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_issue template](
https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
and ensure doc acceptance criteria is met. Link the development issue to
the doc issue. - [ ] Provide input to the QE team, and ensure QE acceptance criteria
(established between story owner and QE focal) are met.
Support Readiness
- [ ] The must-gather script has been updated.