-
Story
-
Resolution: Unresolved
-
Critical
-
ACM 2.13.0
-
3
-
False
-
None
-
False
-
-
-
-
Installer Sprint 2025-50, Installer Sprint 2025-51, Installer Sprint 2025-52
-
None
Value Statement
The import-controller(server foundation component) needs a new field in .values.hubconfig to determine whether flightctl is enabled or not.
The usage of this field would be like this commit: https://github.com/stolostron/backplane-operator/pull/1108/commits/768e94eb4929ad8e2db04ba73da1b49d5b7e1b45
When the control is enabled/disabled, we expect deployment get re-rendered, old pods turn down and new pod spin up.
Definition of Done for Engineering Story Owner (Checklist)
- ...
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 template that you can access from [The Playbook](
and ensure doc acceptance criteria is met.
- Call out this sentence as it's own action:
- [ ] Link the development issue to the doc issue.
Support Readiness
- [ ] The must-gather script has been updated.
- blocks
-
ACM-16325 Enable flightclt support in the import-controller after enable flightctl in MCE.
- Review
- is related to
-
ACM-15689 As an MCH dev, I want to add a toggle for the Edge Management (FlightCTL) deployment in the MCH operator, allowing users to enable or disable the component in the MCH CR
- Review