Bug 2032659

Summary: [RFE] Implement version control for Elasticsearch deployment in Service Telemetry Operator
Product: Service Telemetry Framework Reporter: Leif Madsen <lmadsen>
Component: service-telemetry-operator-containerAssignee: Leif Madsen <lmadsen>
Status: CLOSED ERRATA QA Contact: Leonid Natapov <lnatapov>
Severity: high Docs Contact: Joanne O'Flynn <joflynn>
Priority: high    
Version: 1.4Keywords: Triaged
Target Milestone: GA   
Target Release: 1.4 (STF)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: service-telemetry-operator-container-1.4.0-1 Doc Type: Enhancement
Doc Text:
Add the `backends.events.elasticsearch.version` parameter to the ServiceTelemetry manifest so that the Elasticsearch version requested by STF to the Elasticsearch Operator can be specified.
Story Points: ---
Clone Of:
: 2032661 (view as bug list) Environment:
Last Closed: 2022-01-26 17:01:45 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:
Bug Depends On:    
Bug Blocks: 2032661    

Description Leif Madsen 2021-12-14 22:05:04 UTC
The version of Elasticsearch requested by STF is statically bound to Elasticsearch 7.10.2. It should be possible to configure this as part of the ServiceTelemetry manifest.

Comment 7 errata-xmlrpc 2022-01-26 17:01:45 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Release of components for Service Telemetry Framework 1.4.0 - Container Images), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:0298