Skip to content

[NETOBSERV] OSDOCS-15504 Vale updates to logging-loki-log-access.adoc #96564

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

[NETOBSERV] OSDOCS-15504 Vale updates to logging-loki-log-access.adoc #96564

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions modules/logging-loki-log-access.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@
[id="logging-loki-log-access_{context}"]
= Fine grained access for Loki logs

In {logging} 5.8 and later, the {clo} does not grant all users access to logs by default. As an administrator, you must configure your users' access unless the Operator was upgraded and prior configurations are in place. Depending on your configuration and need, you can configure fine grain access to logs using the following:
In {logging} 5.8 and later, the {clo} does not grant all users access to logs by default. As an administrator, you must configure your users' access unless the Operator was upgraded and prior configurations are in place. Depending on your configuration and need, you can configure fine grain access to logs by using the following:

* Cluster wide policies
* Namespace scoped policies
Expand All @@ -23,7 +23,7 @@ If you have upgraded from a prior version, an additional cluster role `logging-a

[NOTE]
====
Users with access by namespace must provide a namespace when querying application logs.
Users with access by namespace must give a namespace when querying application logs.
====

== Cluster wide access
Expand Down Expand Up @@ -75,14 +75,14 @@ subjects:
== Custom admin group access

// tag::LokiMode[]
If you have a large deployment with several users who require broader permissions, you can create a custom group using the `adminGroup` field. Users who are members of any group specified in the `adminGroups` field of the `LokiStack` CR are considered administrators.
If you have a large deployment with several users who require broader permissions, you can create a custom group by using the `adminGroup` field. Users who are members of any group specified in the `adminGroups` field of the `LokiStack` CR are considered administrators.
// end::LokiMode[]

// tag::NetObservMode[]
If you need to see cluster-wide logs without necessarily being an administrator, or if you already have any group defined that you want to use here, you can specify a custom group using the `adminGroup` field. Users who are members of any group specified in the `adminGroups` field of the `LokiStack` custom resource (CR) have the same read access to logs as administrators.
If you need to see cluster-wide logs without necessarily being an administrator, or if you already have any group defined that you want to use here, you can specify a custom group by using the `adminGroup` field. Users who are members of any group specified in the `adminGroups` field of the `LokiStack` custom resource (CR) have the same read access to logs as administrators.
// end::NetObservMode[]

// tag::LokiMode[]
// tag::LokiMode[]
Administrator users have access to all application logs in all namespaces, if they also get assigned the `cluster-logging-application-view` role.
// end::LokiMode[]

Expand Down