-
Spike
-
Resolution: Done
-
Critical
-
None
-
None
-
False
-
None
-
False
-
-
-
-
No
Value Statement
In ARO HCP case, it is more likely the management cluster will be run on AKS cluster. We need to investigate whether how to install/upgrade MCE+policy addon on AKS cluster
Definition of Done for Engineering Story Owner (Checklist)
- A prototype and proposal to run MCE + policy addon on AKS cluster.
- This must be something we can fully support
Development Complete
- The code is complete.
- The deployment process can be incorporated into a standard pipeline (Azure EV2)
- Functionality is working, and we are able to call out any differences between the shipping product for support
- Any required downstream Docker file changes are made.
- We have had an initial support discussion (CEE or Dev)
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.
- is depended on by
-
ACM-9801 Create a pattern for provisioning ACM on AKS clusters to support ARO-HCP
- Closed