metrics: fix typo in tidb_summary.jsonnet template variable

[boltandrke]

What problem does this PR solve?

Issue Number: close #65589

Problem Summary: The tidb_cluster template variable query references a non-existent variable $kuberentes (typo) instead of $k8s_cluster.

What changed and how does it work?

Fixed the variable reference from $kuberentes to $k8s_cluster in:

• pkg/metrics/grafana/tidb_summary.jsonnet (line 62)
• pkg/metrics/grafana/tidb_summary.json (line 1789)

The $k8s_cluster variable is defined earlier in the dashboard templates.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

None

[ti-chi-bot]

Hi @boltandrke. Thanks for your PR.

I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[ti-chi-bot]

Welcome @boltandrke!

It looks like this is your first PR to pingcap/tidb 🎉.

I'm the bot to help you request reviewers, add labels and more, See available commands.

We want to make sure your contribution gets all the attention it needs!



Thank you, and welcome to pingcap/tidb. 😃

[pingcap-cla-assistant]

All committers have signed the CLA.

[tiprow]

Hi @boltandrke. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

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.

[dveeden]

From the description:

Issue Number: ref #58436

The link goes to a pull request, not an issue. Could you update this. Feel free to create a new issue if needed. This makes it easier to triage and cherry pick to the right branches.

Also, please sign the CLA on https://cla.pingcap.net/pingcap/tidb?pullRequest=65582

[dveeden]

/ok-to-test

[dveeden]

Introduced in cc3c905 / #32546

$ git show cc3c9050134 | grep -B1 kuberentes
-            "query": "label_values(pd_cluster_status, tidb_cluster)",
+            "query": "label_values(pd_cluster_status{k8s_cluster=\"$kuberentes\"}, tidb_cluster)",
--
-    query='label_values(pd_cluster_status, tidb_cluster)',
+    query='label_values(pd_cluster_status{k8s_cluster="$kuberentes"}, tidb_cluster)',

[just1900]

LGTM

[ti-chi-bot]

@just1900: adding LGTM is restricted to approvers and reviewers in OWNERS files.

Details

In response to this:

LGTM

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.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 77.5480%. Comparing base (53dc671) to head (d8a7b76).
⚠️ Report is 9 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #65582        +/-   ##
================================================
- Coverage   77.8520%   77.5480%   -0.3041%     
================================================
  Files          1973       1907        -66     
  Lines        541968     531378     -10590     
================================================
- Hits         421933     412073      -9860     
- Misses       118376     119297       +921     
+ Partials       1659          8      -1651     

Flag	Coverage Δ
integration	41.6050% <ø> (-6.5849%)	⬇️
unit	76.7968% <ø> (+0.3196%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	56.7974% <ø> (ø)
parser	∅ <ø> (∅)
br	48.8272% <ø> (-12.3178%)	⬇️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[dveeden]

/check-issue-triage-complete

[zimulala]

Could you update the pd_cluster_status related content to align with the next-gen in
tidb_summary_with_keyspace_name.json and tidb_summary_with_keyspace_name.jsonnet?

[hawkingrei]

/retest

[dveeden]

/retest

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dveeden, just1900, zimulala

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:

• pkg/metrics/OWNERS [zimulala]

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

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2026-01-15 12:52:29.150839498 +0000 UTC m=+66376.764796344: ☑️ agreed by dveeden.
• 2026-01-16 15:11:01.300615128 +0000 UTC m=+161088.914571974: ☑️ agreed by zimulala.

[dveeden]

/retest

[dveeden]

/retest

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.1: #65612.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #65613.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.1: #65614.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.5: #65615.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.1: #65616.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.5: #65617.