-
Story
-
Resolution: Unresolved
-
Normal
-
Future
-
None
-
False
-
None
-
False
-
-
No
-
-
Value Statement
As we prepare to deploy MCE on an AKS cluster, it's important to ensure that unrelated AKS pecific fields are not included in the component's deployments or other resources. We must ensure that our automation for bundling can effectively handle building configurations across various platforms.
Definition of Done for Engineering Story Owner (Checklist)
- [] Bundle automation can transform the deployment to handle both AKS and OCP resource changes.
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.