From 982cec2e367a103fae6d90a0e98a897a52340d40 Mon Sep 17 00:00:00 2001 From: Chris Sibbitt Date: Tue, 22 Aug 2023 12:44:21 -0400 Subject: [PATCH] Trivial leftover suggestions (#485) * Trivial leftover suggestions --- .../con_primary-parameters-of-the-servicetelemetry-object.adoc | 2 +- .../modules/con_tls-certificates-duration.adoc | 2 +- 2 files changed, 2 insertions(+), 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 f582697b..ba7969c7 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 @@ -110,7 +110,7 @@ spec: [NOTE] ==== -Older versions of {ProjectShort} would manage Elasticsearch objects for the community supported Elastic Cloud on Kuberneters Operator (ECK). This 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 one deployed 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}. +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}. ==== To enable events forwarding to Elasticsearch as a storage back end, you must configure the `ServiceTelemetry` object. diff --git a/doc-Service-Telemetry-Framework/modules/con_tls-certificates-duration.adoc b/doc-Service-Telemetry-Framework/modules/con_tls-certificates-duration.adoc index 75e99c43..881454ac 100644 --- a/doc-Service-Telemetry-Framework/modules/con_tls-certificates-duration.adoc +++ b/doc-Service-Telemetry-Framework/modules/con_tls-certificates-duration.adoc @@ -17,7 +17,7 @@ caCertDuration:: The requested 'duration' or lifetime of the CA Certificate. Minimum accepted duration is 1 hour. Value must be in units accepted by Go time.ParseDuration https://golang.org/pkg/time/#ParseDuration. Default value is `70080h`. -NOTE: The default duration of certificates is long, because you usually copy a subset of them in the {OpenStack} deployment when the certificates renew. For more information about the QDR CA Certificate renewal process, see xref:assembly-renewing-the-amq-interconnect-certificate_assembly[] +NOTE: The default duration of certificates is long, because you usually copy a subset of them in the {OpenStack} deployment when the certificates renew. For more information about the QDR CA Certificate renewal process, see xref:assembly-renewing-the-amq-interconnect-certificate_assembly[]. You can configure the `certificates` parameter for QDR that is part of the `transports.qdr` definition in the `ServiceTelemetry` object: