Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2121457

Summary:	[STF 1.5] Release delivery of STF 1.5 on OCP 4.10
Product:	Service Telemetry Framework	Reporter:	Leif Madsen <lmadsen>
Component:	distribution	Assignee:	Leif Madsen <lmadsen>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Leonid Natapov <lnatapov>
Severity:	high	Docs Contact:	Joanne O'Flynn <joflynn>
Priority:	high
Version:	1.5	CC:	jjoyce, jschluet, lhh, mburns, mgarciac, mgeary, scohen, shrjoshi
Target Milestone:	GA	Keywords:	FutureFeature, Triaged
Target Release:	1.5 (STF)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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].	Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-01-24 22:25:29 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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