-
Spike
-
Resolution: Done
-
Critical
-
Global Hub 1.3.0
Value Statement
Ensure the issue title clearly reflects the value of this spike story.
(Explain the "WHY")
Definition of Done for Engineering Story Owner (Checklist)
- How to deploy global hub agent in ACM (addon or mch.spec)
- How to support globalhub different versionĀ for agent, or support to run 2 global hub agent ?
- Disable some global hub feature (lease, heartbeat, finalizer, per-delete job)
- Different ACM version(globalhub agent) send info to 1 kafka?
- Use which Kafka topic, secret, kafka cert rotate.
- Collect what kind of events?
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.
- relates to
-
ACM-12384 Standalone global hub agent [DP]
- Closed