OU-1077: namespace dropdown fixes

[PeterYurkovich]

This PR looks to make 2 general changes to the codebase:

1. Always use the non-tenacy path for admin users, allowing the queries to do the filtering for admin users. This is accomplished by checking the useMetricsTenancy and useAlertsTenancy values of the useMonitoring hook
2. Ensure useQueryNamespace is called on all pages which need to sync the activeNamespace with a namespace parameter

[openshift-ci-robot]

@PeterYurkovich: This pull request references OU-1081 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 task to target the "4.21.0" version, but no target version was set.

In response to this:

This PR looks to make 2 general changes to the codebase:

1. Always use the non-tenacy path for admin users, allowing the queries to do the filtering for admin users. This is accomplished by checking the useMetricsTenancy and useAlertsTenancy values of the useMonitoring hook
2. Ensure useQueryNamespace is called on all pages which need to sync the activeNamespace with a namespace parameter

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-robot]

@PeterYurkovich: This pull request references OU-1077 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 task to target the "4.21.0" version, but no target version was set.

In response to this:

This PR looks to make 2 general changes to the codebase:

1. Always use the non-tenacy path for admin users, allowing the queries to do the filtering for admin users. This is accomplished by checking the useMetricsTenancy and useAlertsTenancy values of the useMonitoring hook
2. Ensure useQueryNamespace is called on all pages which need to sync the activeNamespace with a namespace parameter

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.

[etmurasaki]

/label qe-approved
tested with the image quay.io/rh-ee-pyurkovi/monitoring-plugin:multi-4

[openshift-ci-robot]

@PeterYurkovich: This pull request references OU-1077 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 task to target the "4.21.0" version, but no target version was set.

In response to this:

This PR looks to make 2 general changes to the codebase:

1. Always use the non-tenacy path for admin users, allowing the queries to do the filtering for admin users. This is accomplished by checking the useMetricsTenancy and useAlertsTenancy values of the useMonitoring hook
2. Ensure useQueryNamespace is called on all pages which need to sync the activeNamespace with a namespace parameter

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]

/hold

[PeterYurkovich]

/remove-label qe-approved

[openshift-ci-robot]

@PeterYurkovich: This pull request references OU-1077 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 task to target the "4.21.0" version, but no target version was set.

In response to this:

This PR looks to make 2 general changes to the codebase:

1. Always use the non-tenacy path for admin users, allowing the queries to do the filtering for admin users. This is accomplished by checking the useMetricsTenancy and useAlertsTenancy values of the useMonitoring hook
2. Ensure useQueryNamespace is called on all pages which need to sync the activeNamespace with a namespace parameter

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]

/unhold

[jgbernalp]

/lgtm

[etmurasaki]

/label qe-approved
solving bug OU-1110 and OU-1109 not rep anymore.

[openshift-ci-robot]

@PeterYurkovich: This pull request references OU-1077 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 task to target the "4.21.0" version, but no target version was set.

In response to this:

This PR looks to make 2 general changes to the codebase:

1. Always use the non-tenacy path for admin users, allowing the queries to do the filtering for admin users. This is accomplished by checking the useMetricsTenancy and useAlertsTenancy values of the useMonitoring hook
2. Ensure useQueryNamespace is called on all pages which need to sync the activeNamespace with a namespace parameter

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.

[jgbernalp]

/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

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

[openshift-ci]

@PeterYurkovich: all tests passed!

Full PR test history. Your PR dashboard.

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.