From 120a9636084cdb1a01f5cdd8ac29a904af75304c Mon Sep 17 00:00:00 2001 From: Chris Sibbitt Date: Thu, 31 Aug 2023 11:57:25 -0400 Subject: [PATCH 1/2] Link ES section to KB article --- ...n_primary-parameters-of-the-servicetelemetry-object.adoc | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/doc-Service-Telemetry-Framework/modules/con_primary-parameters-of-the-servicetelemetry-object.adoc b/doc-Service-Telemetry-Framework/modules/con_primary-parameters-of-the-servicetelemetry-object.adoc index ba7969c7..a9d0ecad 100644 --- a/doc-Service-Telemetry-Framework/modules/con_primary-parameters-of-the-servicetelemetry-object.adoc +++ b/doc-Service-Telemetry-Framework/modules/con_primary-parameters-of-the-servicetelemetry-object.adoc @@ -111,6 +111,12 @@ spec: [NOTE] ==== Older versions of {ProjectShort} would manage Elasticsearch objects for the community supported Elastic Cloud on Kubernetes Operator (ECK). Elasticsearch management functionality is deprecated as of {ProjectShort} 1.5.3. Future versions of Service Telemetry Operator will continue to support forwarding to an existing Elasticsearch instance (which can be deployed and managed by ECK), but will not manage the creation of Elasticsearch objects. When upgrading an {ProjectShort} deployment, any existing Elasticsearch object and deployment will remain intact, but will no longer be managed by {ProjectShort}. + +ifeval::["{build}" == "downstream"] +Refer to this article for additional information about https://access.redhat.com/articles/7031236[Using Service Telemetry Framework with Elasticsearch +] +endif::[] + ==== To enable events forwarding to Elasticsearch as a storage back end, you must configure the `ServiceTelemetry` object. From 037f511eae86152dbc56ce78076070a362120ade Mon Sep 17 00:00:00 2001 From: Leif Madsen Date: Tue, 5 Sep 2023 11:31:30 -0400 Subject: [PATCH 2/2] Update doc-Service-Telemetry-Framework/modules/con_primary-parameters-of-the-servicetelemetry-object.adoc --- .../con_primary-parameters-of-the-servicetelemetry-object.adoc | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/doc-Service-Telemetry-Framework/modules/con_primary-parameters-of-the-servicetelemetry-object.adoc b/doc-Service-Telemetry-Framework/modules/con_primary-parameters-of-the-servicetelemetry-object.adoc index a9d0ecad..42637a6f 100644 --- a/doc-Service-Telemetry-Framework/modules/con_primary-parameters-of-the-servicetelemetry-object.adoc +++ b/doc-Service-Telemetry-Framework/modules/con_primary-parameters-of-the-servicetelemetry-object.adoc @@ -113,8 +113,7 @@ spec: Older versions of {ProjectShort} would manage Elasticsearch objects for the community supported Elastic Cloud on Kubernetes Operator (ECK). Elasticsearch management functionality is deprecated as of {ProjectShort} 1.5.3. Future versions of Service Telemetry Operator will continue to support forwarding to an existing Elasticsearch instance (which can be deployed and managed by ECK), but will not manage the creation of Elasticsearch objects. When upgrading an {ProjectShort} deployment, any existing Elasticsearch object and deployment will remain intact, but will no longer be managed by {ProjectShort}. ifeval::["{build}" == "downstream"] -Refer to this article for additional information about https://access.redhat.com/articles/7031236[Using Service Telemetry Framework with Elasticsearch -] +Refer to this article for additional information about https://access.redhat.com/articles/7031236[Using Service Telemetry Framework with Elasticsearch] endif::[] ====