Skip to content

Commit 9e0911d

Browse files
committed
OSDOCS-13703:Fixed callout rendering issue in Understanding config map doc.
1 parent 03af5b1 commit 9e0911d

File tree

3 files changed

+11
-2
lines changed

3 files changed

+11
-2
lines changed

Diff for: modules/nodes-pods-secrets-certificates-creating.adoc

+1-1
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ spec:
3535
targetPort: 9376
3636
----
3737
+
38-
The certificate and key are in PEM format, stored in `tls.crt` and `tls.key`
38+
<1> The certificate and key are in PEM format, stored in `tls.crt` and `tls.key`
3939
respectively.
4040

4141
. Create the service:

Diff for: observability/logging/cluster-logging.adoc

+9
Original file line numberDiff line numberDiff line change
@@ -15,10 +15,19 @@ include::snippets/logging-kibana-dep-snip.adoc[]
1515

1616
The Operators are responsible for deploying, upgrading, and maintaining {logging}. After the Operators are installed, you can create a `ClusterLogging` custom resource (CR) to schedule {logging} pods and other resources necessary to support {logging}. You can also create a `ClusterLogForwarder` CR to specify which logs are collected, how they are transformed, and where they are forwarded to.
1717

18+
ifndef::openshift-rosa,openshift-dedicated[]
1819
[NOTE]
1920
====
2021
Because the internal {product-title} Elasticsearch log store does not provide secure storage for audit logs, audit logs are not stored in the internal Elasticsearch instance by default. If you want to send the audit logs to the default internal Elasticsearch log store, for example to view the audit logs in Kibana, you must use the Log Forwarding API as described in xref :../../observability/logging/log_storage/logging-config-es-store.adoc#cluster-logging-elasticsearch-audit_logging-config-es-store[Forward audit logs to the log store].
2122
====
23+
endif::openshift-rosa,openshift-dedicated[]
24+
25+
ifdef::openshift-rosa,openshift-dedicated[]
26+
[NOTE]
27+
====
28+
Because the internal {product-title} Elasticsearch log store does not provide secure storage for audit logs, audit logs are not stored in the internal Elasticsearch instance by default. If you want to send the audit logs to the default internal Elasticsearch log store, for example to view the audit logs in Kibana, you must use the Log Forwarding API as described in link:observability/logging/log_storage/logging-config-es-store.adoc#cluster-logging-elasticsearch-audit_logging-config-es-store[Forward audit logs to the log store].
29+
====
30+
endif::openshift-rosa,openshift-dedicated[]
2231

2332
include::modules/logging-architecture-overview.adoc[leveloffset=+1]
2433

Diff for: snippets/logging-kibana-dep-snip.adoc

+1-1
Original file line numberDiff line numberDiff line change
@@ -10,5 +10,5 @@
1010

1111
[NOTE]
1212
====
13-
The Kibana web console is now deprecated is planned to be removed in a future logging release.
13+
The Kibana web console is now deprecated and is planned to be removed in a future logging release.
1414
====

0 commit comments

Comments
 (0)