OU-1144: fix: request namespaced resources for filter options

[jgbernalp]

No description provided.

[openshift-ci-robot]

@jgbernalp: This pull request references OU-1144 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[PeterYurkovich]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jgbernalp, PeterYurkovich

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [PeterYurkovich,jgbernalp]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[jgbernalp]

/retest

[openshift-ci]

New changes are detected. LGTM label has been removed.

[etmurasaki]

/label qe-approved
comments in jira.

[openshift-ci-robot]

@jgbernalp: This pull request references OU-1144 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

@jgbernalp: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[anpingli]

/hold

[anpingli]

@jgbernalp I can’t see pods whose logs are not being sent out. Is that correct? Do we want to display all pods no matter logs are sent to loki or not ?

[jgbernalp]

@anpingli yes. This will be an indicator that something is wrong with the collector or the application producing logs not reaching loki. We merge the k8s api results with loki labels results, to show resources without logs or deleted resources logs.

[anpingli]

@jgbernalp the bold lines below are not as expected.

when log in as kubeadmin,

the namespaces can be displayed base on tenant. that is correct
the pods/containers can not be displayed base on tenant. that is wrong.
there are new pods (Logs weren't sent into lokistack) in AdminConsole ->Observe->logs. That is correct.
there is not new pod(Logs weren't sent into lokistack) in DevConsole->Observe->logs. That is wrong.
there is not new pod(Logs weren't sent into lokistack) in AdminConsole ->pod->Agg Logs. That should be correct.
there is not new pod(Logs weren't sent into lokistack) in DevConsole-> pod->Agg Logs. That should be correct.

when log in as non-cluster-admin users with role below

oc adm policy add-cluster-role-to-user view ${user_name}
oc adm policy add-cluster-role-to-user cluster-logging-application-view ${user_name}
oc adm policy add-cluster-role-to-user cluster-logging-audit-view ${user_name}
oc adm policy add-cluster-role-to-user cluster-logging-infrastructure-view ${user_name}
oc adm policy add-cluster-role-to-user monitoring-rules-edit ${user_name}
oc adm policy add-cluster-role-to-user cluster-monitoring-view ${user_name}

the namespaces can be displayed base on tenant. that is correct.
the pods/containers can be displayed base on tenant. that is correct.
there are new pods (Logs weren't sent into lokistack) in AdminConsole ->Observe->logs. That is correct.
there is not new pod(Logs weren't sent into lokistack) in DevConsole->Observe->logs. That is wrong.
there is not new pod(Logs weren't sent into lokistack) in AdminConsole ->pod->Agg Logs. That should be correct.
there is not new pod(Logs weren't sent into lokistack) in DevConsole-> pod->Agg Logs. That should be correct.

Step to test:

1. Send pods logs in namespace1 to lokistack
2. Delete the pod in namespace1
3. remove CLF
4. create new pods in namespace1
5. create new namespace2 and pods in this namespace

Expected Result:
The namespaces, pods, containers can be displayed base on tenant.
All pods ( deleted, running and pods whose logs are not in lokistack) can be displayed in Attribute-options in observe-> Log

Actual Result:
we can not see new pods in AttributeOptions in some cases.

[anpingli]

/canel qe-approved