Bug 1977958
| Summary: | [RFE] Deployment without storage backends | ||
|---|---|---|---|
| Product: | Service Telemetry Framework | Reporter: | Leif Madsen <lmadsen> |
| Component: | service-telemetry-operator-container | Assignee: | Leif Madsen <lmadsen> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Leonid Natapov <lnatapov> |
| Severity: | medium | Docs Contact: | Joanne O'Flynn <joflynn> |
| Priority: | low | ||
| Version: | 1.3 | CC: | mrunge |
| Target Milestone: | GA | Keywords: | FutureFeature, Triaged |
| 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: |
Service Telemetry Framework (STF) now supports a new parameter to the ServiceTelemtry manifest, `observabilityStrategy`.
Setting the parameter observabilityStrategy to a value of "none" results in the Service Telemetry Operator deploying the AMQ Interconnect routers, and the Smart Gateways for metrics and sensubility (API monitoring).
When you set the observabilityStrategy parameter to "none", the administrator can deploy STF in a minimal configuration, which results in the consumption of telemetry data from Red Hat OpenStack Platform to be exposed in OpenShift Container Platform through the Smart Gateway.
It is currently not possible to deploy the event Smart Gateways in this mode.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-02-03 14:27:56 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
2021-06-30 19:36:24 UTC
Changes merged upstream. |