Discrepency between "cluster flow/flows" etc is out of my control for the UI string changes.

You can remove 99 in harvesterhci.io.logging.clusterflow.vue to keep label/For getter use default count = 1 to get typeDisplay (list page title)

 return this.$store.getters['type-map/labelFor'](schema);

Same for harvesterhci.io.logging.clusteroutput.vue / flow.vue / output.vue

Currently unable to chagne the message "VirtualMachine generation is 2..."

Hi @Yu-Jack or @FrankYang0529 ,

Could you kindly help separate the wording "VirtualMachine" to "Virtual Machine" in harvester/vendor/sigs.k8s.io/cli-utils/pkg/kstatus/status/generic.go ?

Currently unable to chagne the message "VirtualMachine generation is 2..."

Hi @Yu-Jack or @FrankYang0529 ,

Could you kindly help separate the wording "VirtualMachine" to "Virtual Machine" in harvester/vendor/sigs.k8s.io/cli-utils/pkg/kstatus/status/generic.go ?

Hi @a110605, we may not be able to do that. harvester/vendor/sigs.k8s.io/cli-utils/pkg/kstatus/status/generic.go is upstream code. Also, VirtualMachine is defined in upstream.

BTW, it's a Kind, so it's slightly different meaning between VirtualMachine and Virtual Machine.

“VirtualMachine” in “VirtualMachine generation is 2...” means that this resource is in k8s. “Virtual Machine” means that we usually used it to describe about VM. So, I suggest not to revise this word.

“VirtualMachine” in “VirtualMachine generation is 2...” means that this resource is in k8s. “Virtual Machine” means that we usually used it to describe about VM. So, I suggest not to revise this word.

Hmm I understand. That being said, because it's the same text, it looks like a spelling mistake. Can we apply some mark-up to 'VirtualMachine' to ensure it's clear?

“VirtualMachine” in “VirtualMachine generation is 2...” means that this resource is in k8s. “Virtual Machine” means that we usually used it to describe about VM. So, I suggest not to revise this word.

Hmm I understand. That being said, because it's the same text, it looks like a spelling mistake. Can we apply some mark-up to 'VirtualMachine' to ensure it's clear?

Hi @Yu-Jack , could you help from backend side?

Hi @a110605. Just like @FrankYang0529 mentioned, it's an upstream code, we can't modify it. So, you probably need to handle it in frontend code for this specific case.

“VirtualMachine” in “VirtualMachine generation is 2...” means that this resource is in k8s. “Virtual Machine” means that we usually used it to describe about VM. So, I suggest not to revise this word.

Hmm I understand. That being said, because it's the same text, it looks like a spelling mistake. Can we apply some mark-up to 'VirtualMachine' to ensure it's clear?

Quick synced with @Yu-Jack , we don't want to have any change in generic.go, since it's upstream code. cc @bk201

@asettle, can we skip this wording revision or we want to add specific logic in frontend to handle this wording ?

BTW, that message is from https://github.com/kubernetes-sigs/cli-utils/blob/0a569f59bebe08eb86f0fb530741343b10e01249/pkg/kstatus/status/generic.go#L90.

“VirtualMachine” in “VirtualMachine generation is 2...” means that this resource is in k8s. “Virtual Machine” means that we usually used it to describe about VM. So, I suggest not to revise this word.

Hmm I understand. That being said, because it's the same text, it looks like a spelling mistake. Can we apply some mark-up to 'VirtualMachine' to ensure it's clear?

Quick synced with @Yu-Jack , we don't want to have any change in generic.go, since it's upstream code. cc @bk201

@asettle, can we skip this wording revision or we want to add specific logic in frontend to handle this wording ?

We can skip. It'll suffice for now. We can create a bug to handle this in later versions.

@asettle , I check QA reported unfinished items and seems we are still missing some items

• 1). rancher monitoring (Addon: rancher-monitoring) is this Addon should be hyphenated ?
• 3). Alert manager configs contradicts with Alert Manager configurations
• 4).Logging (cluster Flow,cluster output,flow,output) contradicts with (cluster Flows.cluster Outputs,Flows,outputs) <- sorry, we should follow other resources to use plural wordings.
• 6). Settings description (Typical users...) not changed as expected in the bug <- (should add new wording in harvester en-us.yaml)

Pushed my 3 commits in this PR. Please check and test them, thx