fix: Make global values compatible with new collectors

[denis-ryzhkov]

• Making global values DRY and simple by:
  • deleting the duplicates hardcoded in MCS-es,
  • passing -f global-values.yaml on direct helm install,
  • passing --set-file globalValues=global-values.yaml on helm install via MCS-es.
• Tested:

helm template kof-regional ./charts/kof-regional \
  --set-file globalValues=global-values.yaml > kof-regional-rendered.yaml

helm template kof-child ./charts/kof-child \
  --set-file globalValues=global-values.yaml > kof-child-rendered.yaml

• Result:
  • global-values.yaml
  • kof-child-rendered.yaml
  • kof-regional-rendered.yaml

[Copilot]

Pull request overview

This PR simplifies global values handling in Helm charts by eliminating duplication. Instead of embedding hardcoded registry override logic in each Multi-Cluster Service (MCS) template, the charts now accept a globalValues parameter that can be passed directly via --set-file or -f flags during Helm installation.

Key changes:

• Removed duplicate hardcoded global values logic from MCS templates
• Added globalValues: {} parameter to chart values files
• Simplified registry override logic to read from the new parameter

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.

File	Description
charts/kof-regional/values.yaml	Added globalValues parameter to support external global values injection
charts/kof-regional/templates/regional-multi-cluster-service.yaml	Replaced hardcoded registry override logic with simpler logic using globalValues parameter
charts/kof-child/values.yaml	Added globalValues parameter to support external global values injection
charts/kof-child/templates/child-multi-cluster-service.yaml	Replaced hardcoded registry override logic with simpler logic using globalValues parameter