Workload status with black graphs in DE, ES, FR and ZH

[vittoriocanilli]

What happened?

If I set the language in my local settings to German, Spanish, French or Chinese Simplified the graphs in the workload status window are black:

What did you expect to happen?

I expect them to be green, like in the other languages: English, Korean, Japanese, Chinese Traditional and Chinese Traditional Hong Kong.

How can we reproduce it (as minimally and precisely as possible)?

Simply set your local settings to German, Spanish, French or Chinese Simplified and then go to the workload status window

Anything else we need to know?

I see that the same bug was reported in the past for Japanese and Korean, and it was solved back then:

• The status dashboard displays black for some languages #7605
• The workload status indication graph is displayed in black. #8321

What browsers are you seeing the problem on?

Chrome

Kubernetes Dashboard version

7.3.0

Kubernetes version

1.27.7

Dev environment

No response

[romain-rossi]

Probably related to the issue #8753 since the version 7.0.0

[vittoriocanilli]

Thanks @romain-rossi I did not find your issue when I searched. Let's hope that the maintainers reply to one of us 😄

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[vittoriocanilli]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[vittoriocanilli]

/remove-lifecycle rotten