fix: workload charts are black for certain languages

[HanNguyen-dev]

For certain languages such as KR and FR, the workload charts are black.

The current code is pulling out the translation for the different statuses by passing Running, Succeeded, etc; just that there are different texts (3) starting with Running, Succeeded, etc.

The code change passes in an empty string for placeholder to mimic how status label names were generated; thus the translated text will be a substring of the status label names.

dashboard/modules/web/src/overview/helper.ts

Lines 30 to 34 in 5d6805d

	let items = [
	{
	name: $localize`Running: ${status.running}`,
	value: (status.running / totalItems) * 100,
	},

Steps to reproduce bug (french)

See commit HanNguyen-dev@8ca2535 for details

In the angular.json

1. Add new build configuration for development and fr

      "development": {
          "localize": false,
          "optimization": false,
          "extractLicenses": false,
          "sourceMap": true
      },
      "fr": {
          "localize": ["fr"],
      },

2. Add new serve configuration

       "configurations": {
          "fr": {
             "browserTarget": "kubernetes-dashboard:build:development,fr"
          }
       }

In the dev.serve.sh

dashboard/modules/web/hack/scripts/dev.serve.sh

Line 21 in 4f3d800

npx ng serve --proxy-config=proxy.conf.json --host=0.0.0.0 --disable-host-check --poll=2000

1. Pass in the --configuration=fr.

npx ng serve --proxy-config=proxy.conf.json --configuration=fr --host=0.0.0.0 --disable-host-check --poll=2000

Run make serve

Screenshots

Before

After

---

closes #8898
closes #8753

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: HanNguyen-dev / name: Han Nguyen (4934250, 02dd071, fc0fa51)

[k8s-ci-robot]

Welcome @HanNguyen-dev!

It looks like this is your first PR to kubernetes/dashboard 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/dashboard has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[Amphaal]

Nice fix @HanNguyen-dev, thanks. LFT it being merged !

[gdelvallez1]

I agree , it is a nice fix. It will Help to fix the issue in all languages at once.
/lgtm

[k8s-ci-robot]

@gdelvallez1: changing LGTM is restricted to collaborators

In response to this:

I agree , it is a nice fix. It will Help to fix the issue in all languages at once.
/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.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: gdelvallez1, HanNguyen-dev
Once this PR has been reviewed and has the lgtm label, please assign floreks for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

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

[vittoriocanilli]

Nice fix, @HanNguyen-dev !
Do you know why it is not going through?
Does it maybe need the review from @maciaszczykm or @shu-mutou ?

[HanNguyen-dev]

Hi @vittoriocanilli, I forgot that this PR is still here. I am not familiar with PR process to be honest, but I'll go through their documentation to see what is missing.

I'll pull the latest from master as well, and add some steps to reproduce this bug locally.

[HanNguyen-dev]

/assign @maciaszczykm
/assign @shu-mutou

Can you review this PR? Thanks