We have noticed an instance of incorrect helming in one of your Kubernetes configuration files. Hardcoded or default configuration values in the template are considered anti-pattern and configurable values in the values.yaml file are not being respect, resulting in user-provided configurations never being applied. Additionally, we provide anecdotal evidence from trivy-operator#729 regarding the incorrect helming defect.
image.registry does not take effect when changed to a value other than default value 'docker.io'. This is due to missing implementation for this value in helm charts deploy.yaml file:
We have noticed an instance of incorrect helming in one of your Kubernetes configuration files. Hardcoded or default configuration values in the template are considered anti-pattern and configurable values in the values.yaml file are not being respect, resulting in user-provided configurations never being applied. Additionally, we provide anecdotal evidence from trivy-operator#729 regarding the incorrect helming defect.
image.registry does not take effect when changed to a value other than default value 'docker.io'. This is due to missing implementation for this value in helm charts deploy.yaml file:
https://github.com/apache/dubbo-admin/blob/7bca862a7d13d7f20ce415b15bfa71d4ead88d16/charts/dubbo-admin/templates/deploy.yaml#L25
Environment
Steps to reproduce this issue
Pls. provide [GitHub address] to reproduce this issue.
Expected Result
change image.registry can take affect, or delete image.registry from values.yaml file
Actual Result
image.registry always be 'docker.io'
If there is an exception, please attach the exception trace: