Bug 2121457 - [STF 1.5] Release delivery of STF 1.5 on OCP 4.10
Summary: [STF 1.5] Release delivery of STF 1.5 on OCP 4.10
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Service Telemetry Framework
Classification: Red Hat
Component: distribution
Version: 1.5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 1.5 (STF)
Assignee: Leif Madsen
QA Contact: Leonid Natapov
Joanne O'Flynn
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-25 14:02 UTC by Leif Madsen
Modified: 2023-01-24 22:25 UTC (History)
8 users (show)

Fixed In Version: smart-gateway-operator-bundle-container-5.0.1668472342-1 service-telemetry-operator-bundle-container-1.5.1668472323-1
Doc Type: Release Note
Doc Text:
Service Telemetry Framework (STF) 1.5.0 supports OpenShift Container Platform 4.10. Previous releases of STF were limited to OpenShift Container Platform 4.8, which is nearing the end of extended support. OpenShift Container Platform 4.10 is an Extended Update Support (EUS) release with full support until November 2022, and maintenance support until September 2023. For more information, see https://access.redhat.com/support/policy/updates/openshift[Red Hat OpenShift Container Platform Life Cycle Policy].
Clone Of:
Environment:
Last Closed: 2023-01-24 22:25:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker STF-1079 0 None None None 2022-09-13 16:27:09 UTC

Description Leif Madsen 2022-08-25 14:02:51 UTC
Tracking epic for release of STF 1.5 which will provide support for OCP 4.10. Purpose of this epic is to result in the delivery of artifacts to RHCC by configuring the appropriate release pipelines to allow upstream code to be packaged and delivered.

Overview of tasks covering this epic:

- upstream
-- upstream branching for next set of component release
-- tagging of components for import
-- updating base images to newer releases
- code import
-- update midstream configuration to import appropriate branches
-- refine configuration to target tags closer to Beta release
- pipeline setup
-- configure CPaaS for orchestration of pipeline for delivery via errata
- builds
-- verify all components are built and targeting appropriate versions
-- verify builds 
- operator updates
-- metadata updates to CSV, API references, CRDs, version reference updates, etc
-- update container tagging references
-- adjust any scripting to result in bundles


Note You need to log in before you can comment on or make changes to this bug.