-
Story
-
Resolution: Duplicate
-
Major
-
ACM 2.8.0, MCE 2.3.0
-
None
Value Statement
The hypershift feature for agent and AWS platforms will be GA in MCE 2.3 and ACM 2.8. We need to ensure that the feature works in proxy and disconnected environments.
Definition of Done for Engineering Story Owner (Checklist)
- The hypershift addon agent works in proxied environment.
- The hypershift addon agent works in disconnected environment.
- Hosted clusters with AWS can be created in proxied environment.
- Hosted clusters with BareMetal can be created in proxied environment.
- Hosted clusters with AWS can be created in disconnected environment.
- Hosted clusters with BareMetal can be created in disconnected environment.
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 cloned by
-
ACM-3981 Documentation: Hypershift doc for proxy and disconnected environments
- Closed
1.
|
[QE] ACM-3977: QE: Hypershift test in proxy and disconnected environments | Closed | Unassigned | ||
2.
|
[QE Automation] ACM-3977: QE: Hypershift test in proxy and disconnected environments | Closed | Unassigned |