-
Task
-
Resolution: Done
-
Normal
-
None
-
False
-
None
-
False
-
-
-
-
None
Value Statement
We want our customer to move from AppSub to GitopsOperator.
When the release ACM 2.13 it must be mentioned that AppSub is deprecated, that no new features will be added
and that we are more than happy to talk with our customer on how to migrate.
It should be also be part of statement that we understand that this migration takes time.
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_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 related to
-
ACM-17556 ACM AppSub Add deprecated after Subscription in Application create menu
-
- Closed
-
Deprecation Announcement should be here:
https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.12/html/applications/managing-applications#managing-applications
NOTE: RHACM AppSub feature will be deprecated.
RHACM Application-Lifecycle-Management will be based on OpenShift Gitops-Operator (ArgoCD) with enhanced integration, link to ACM Gitops doc
We expect Application-Subcription-Feature to remain available in the product for about 5 more releases