Bug 1490391

3. What is the nature and description of the request?
While viewing logs in Kibana, a user without permissions to view any pod's logs will have access just by having permissions to see a project. This is just by being able to perform the "view" verb on the resource "namespace". However, it is not being taken into consideration the possibility that some users don't have access to "view" the following resources:
 "pods/log"
 "builds/log"
 "deploymentconfigs/log"

This is why the way currently Elasticsearch + SearchGuard allows a user to access logs is not sufficient.

4. Why does the customer need this? (List the business requirements here)
Given the company's security constrains not everyone administering the cluster has access to the sensitive data like secrets or logs. Those "restricted-admins" have access to the namespaces but must not have access to the logs.

5. How would the customer like to achieve this? (List the functional requirements here)
- As a "cluster-admin" I want to be able to restrict who has access to pods logs even though they have access to the namespace.
- As a "restricted-admin" I shouldn't be able to see pods logs in Kibana the same way I don't have access to them using OpenShift CLI


6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
Given the attached cluster roles and a user having assigned the cluster role "cluster-restricted-admin", this user will not be able to see any logs from any pod.
However if the user is somehow granted the permissions to see certain pods logs, those pods will be shown in Kibana

10. List any affected packages or components.
Aggregated logging framework