From d8c2862f79640fbd1651838a00a9f50adbe57854 Mon Sep 17 00:00:00 2001 From: Leif Madsen Date: Thu, 2 Nov 2023 15:13:12 -0400 Subject: [PATCH] Update doc-Service-Telemetry-Framework/modules/con_stf-architecture.adoc Co-authored-by: mickogeary --- .../modules/con_stf-architecture.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc-Service-Telemetry-Framework/modules/con_stf-architecture.adoc b/doc-Service-Telemetry-Framework/modules/con_stf-architecture.adoc index 513485d3..b02e265d 100644 --- a/doc-Service-Telemetry-Framework/modules/con_stf-architecture.adoc +++ b/doc-Service-Telemetry-Framework/modules/con_stf-architecture.adoc @@ -84,7 +84,7 @@ When you collect and store events, collectd and Ceilometer deliver event data to ==== In previous releases of {ProjectShort}, the Service Telemetry Operator requested instances of Elasticsearch from the Elastic Cloud on Kubernetes (ECK) Operator. {ProjectShort} now uses a forwarding model, where events are forwarded from a Smart Gateway instance to a user-provided instance of Elasticsearch. The management of an Elasticsearch instance by Service Telemetry Operator is deprecated. -New ServiceTelemetry instances will use the `observabilityStrategy` of `use_redhat` which does not request Elasticsearch instances from ECK. Instances of ServiceTelemetry deployed prior to {ProjectShort} 1.5.3 use an observabilityStrategy of use_community, which matches the previous architecture. In the case where a user previously deployed an Elasticsearch instance with {ProjectShort}, the Service Telemetry Operator will automatically update the ServiceTelemetry custom resource object to have the observabilityStrategy set to use_community, and remain functioning the same as previous releases. For more information about observability strategies, see xref:observability-strategy-in-service-telemetry-framework_assembly-preparing-your-ocp-environment-for-stf[]. +In new `ServiceTelemetry`deployments, the `observabilityStrategy` parameter has a value of `use_redhat`, that does not request Elasticsearch instances from ECK. Deployments of `ServiceTelemetry` that are version {ProjectShort} 1.5.3 or older have the `observabilityStrategy` parameter set to `use_community`, which matches the previous architecture. If a user deployed an Elasticsearch instance with {ProjectShort}, the Service Telemetry Operator updates the `ServiceTelemetry` custom resource object to have the `observabilityStrategy` parameter set to `use_community`, and function similar to previous releases. For more information about observability strategies, see xref:observability-strategy-in-service-telemetry-framework_assembly-preparing-your-ocp-environment-for-stf[]. A user can migrate to the use_redhat observability strategy. For more information, see link:https://access.redhat.com/articles/7011708[Migrating Service Telemetry Framework to fully supported operators]. ====