-
Story
-
Resolution: Unresolved
-
Major
-
None
-
5
-
False
-
None
-
False
-
-
-
-
5
-
SF Train-18, SF Train-19
-
None
Value Statement
Ensure the issue title clearly reflects the value of this user story to the
intended persona. (Explain the "WHY")
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.
- relates to
-
ACM-14417 Support verification of the hub API server certification using the system trust store
- Closed
-
ACM-14559 Update the doc of proxy setting and custom url/ca with the refined KlusterletConfig API
- Closed
-
ACM-14566 Create a known issue and troubleshooting guide for ROSA HCP
- Closed
-
ACM-14756 Add API doc for KlusterletConfig
- Closed
-
ACM-14757 Deprecate the legacy fields of klusterletConfig
- Closed
- links to