-
Spike
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
None
-
False
-
None
-
False
-
-
-
No
Value Statement
The AMI with controlplane can be running in t3.small AMI ($182.21/yr) in users account(AWS, Azure, GCP) to provide the control plane capability
Definition of Done for Engineering Story Owner (Checklist)
- The controlplane is managed by systemd
- Introduce `config.yaml` with default values for controlplane. It can be customized. Restart the controlplane service to take affect.
- Expose the controlplane API so that it can be accessed outside
- Deliver it as AMI in AWS only for first phase
- How to handle the cert rotation?
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.