-
Epic
-
Resolution: Done
-
Critical
-
None
-
None
-
None
-
None
-
Support disconnected for RHODS on prem deployment
-
False
-
None
-
False
-
No
-
To Do
-
No
-
Pending
-
None
Clone for epics and close what is not needed
Things to consider and add to the below branches as needed:
- Implement component testing framework (for new components)
- Add tutorials and documentation to ODH website
- Implement Monitoring
- All new features/components must have an upgrade strategy:
- Base language version (e.g. golang versions will be aligned with openshift core components or only use LTS).
- Dependencies
- Write standard operating procedures for new feature for SRE
- Static analysis for new repos
- For static analysis, we are working with QE on what framework is best.
- Blog post about new feature and component
- Record new feature and post to youtube
- What open source projects could come out of this work
- Does it impact any Tier 2 component integration that we need to make the owners of those components aware of?
- For new components:
- Update/create a standard operating procedures document for MT-SRE. Example SOP . Check with SRE team and AI services managers.
- Update/create training material. Dave Mulford is a good contact for this.
- clones
-
RHODS-4911 RHODS - Template For Epics
- New