Skip to content

Commit 0f8600f

Browse files
Merge pull request #74830 from libander/OBSDOCS-797-correction
Correction of #73846
2 parents 5bc3f8a + 57f3953 commit 0f8600f

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

logging/log_storage/installing-log-storage.adoc

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,15 +26,17 @@ include::modules/loki-create-object-storage-secret-console.adoc[leveloffset=+2]
2626
.Additional resources
2727
* xref:../../logging/log_storage/installing-log-storage.adoc#logging-loki-storage_installing-log-storage[Loki object storage]
2828

29+
ifdef::openshift-enterprise[]
2930
[id="installing-log-storage-loki-sts"]
3031
== Deploying a Loki log store on an STS enabled cluster
3132

32-
For cloud based storage, you can use the xref:/../../authentication/managing_cloud_provider_credentials/cco-short-term-creds.adoc[Cloud Credential Operator (CCO)] and CCO utility (`ccoctl`) to configure authentication for your {logging} object store.
33+
For some storage providers, you can use the CCO utility (`ccoctl`) during installation to implement short-term credentials. These credentials are created and managed outside the {product-title} cluster. xref:../../authentication/managing_cloud_provider_credentials/cco-short-term-creds.adoc#cco-short-term-creds[Manual mode with short-term credentials for components].
3334

3435
[NOTE]
3536
====
3637
STS authentication must be configured during a new installation of {loki-op}, on an STS enabled cluster. You cannot configure an existing cluster that uses a different credentials strategy to use this feature.
3738
====
39+
endif::[]
3840

3941
include::modules/logging-identity-federation.adoc[leveloffset=+2]
4042

0 commit comments

Comments
 (0)