Bug 2092544 - [RFE] Expose certificate duration in Certificate object for Interconnect
Summary: [RFE] Expose certificate duration in Certificate object for Interconnect
Alias: None
Product: Service Telemetry Framework
Classification: Red Hat
Component: distribution
Version: 1.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: z1
: 1.5 (STF)
Assignee: Victoria Martinez de la Cruz
QA Contact: Leonid Natapov
Depends On:
TreeView+ depends on / blocked
Reported: 2022-06-01 19:11 UTC by Leif Madsen
Modified: 2023-03-30 00:44 UTC (History)
7 users (show)

Fixed In Version: service-telemetry-operator-container-1.5.1-2
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed: 2023-03-30 00:44:04 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker STF-1055 0 None None None 2022-06-01 19:19:40 UTC

Description Leif Madsen 2022-06-01 19:11:27 UTC
Description of problem: When creating the Interconnect manifest via Service Telemetry Operator, the duration of the certificate is not exposed to the `generateCaCert` parameter, resulting in certificates being created with a default expiration time of 90 days.

The result of this is that in RHOSP 13 and RHOSP 17.0 deployments using SSL configuration for the metrics_qdr service, a cloud update needs to be performed every 90 days with the new CA certificate contents to allow for data to transit the QDR bus to STF.

As part of the certificate manager refectoring and migration, we should allow control of the certificate duration so that it can be more than 90 days before certificates are rotated.

Version-Release number of selected component (if applicable): STF 1.3 and STF 1.4, AMQ Interconnect, AMQ Cert Manager

How reproducible: Always

Comment 2 Leif Madsen 2023-03-27 18:19:17 UTC
Updating this to have a FIV for the STF 1.5.1 release and moving to VERIFIED.

Comment 7 errata-xmlrpc 2023-03-30 00:44:04 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 (Moderate: Service Telemetry Framework 1.5 security update), and where to find the updated
files, follow the link below.

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


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