-
Notifications
You must be signed in to change notification settings - Fork 153
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.
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
Use regex for hostnames in seed MLA dashboard "Resource Usage per Namespace" #12816
Use regex for hostnames in seed MLA dashboard "Resource Usage per Namespace" #12816
Conversation
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
/approve |
LGTM label has been added. Git tree hash: 2cda6daeb4abedb1b0db5027047baee07af462bd
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: wurbanski 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:
Approvers can indicate their approval by writing |
/cherry-pick release/v2.23 |
/cherry-pick release/v2.22 |
@embik: new pull request created: #12832 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 kubernetes/test-infra repository. |
@embik: #12816 failed to apply on top of branch "release/v2.22":
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 kubernetes/test-infra repository. |
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
What this PR does / why we need it:
The "Resource Usage per Namespace" dashboard in our Seed MLA stack supports selecting multiple hosts (and defaults to the "all" option). Some queries were not using the
$hostname
variable as regex, and were therefore failing for every selection except a single host.This was initially reported to us in INC-6148.
Which issue(s) this PR fixes:
Fixes #
What type of PR is this?
/kind bug
Special notes for your reviewer:
Does this PR introduce a user-facing change? Then add your Release Note here:
Documentation: