Bug 1779133 - Can't find customer metrics from thanos-querier in multitenant clusternetwork cluster
Summary: Can't find customer metrics from thanos-querier in multitenant clusternetwork...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.4.0
Assignee: Juan Luis de Sousa-Valadas
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-03 11:38 UTC by Junqi Zhao
Modified: 2020-05-13 21:53 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-13 21:53:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-network-operator pull 415 0 'None' closed Bug 1779133: sdn: Make openshift-user-workload-monitoring global on multitenant 2020-05-04 10:31:53 UTC
Red Hat Product Errata RHBA-2020:0581 0 None None None 2020-05-13 21:53:44 UTC

Comment 11 Casey Callendrello 2019-12-04 10:07:53 UTC 
Assigning to Juan. We can fix this in 4.4 and cherry-pick to 4.3.

Juan, can you please chat with Sergiusz, determine the exact name of the namespace, then add it to bindata/network/openshift-sdn/004-multitenant.yaml please?
Comment 12 Juan Luis de Sousa-Valadas 2019-12-04 11:53:45 UTC 
Sergiusz, sure, it can be done.
Just to confirm, you only want the openshift-monitoring project to be able to access the whole cluster, correct?
Comment 18 errata-xmlrpc 2020-05-13 21:53:42 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0581
Note You need to log in before you can comment on or make changes to this bug.