You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Service.type does not take effect when changed to a value other than default value 'ClusterIP'. This is due to missing implementation for this value in metric server service.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.
Service.type does not take effect when changed to a value other than default value 'ClusterIP'. This is due to missing implementation for this value in metric server service.yaml file:
charts/keda/templates/metrics-server/service.yaml
Line 28 in 43b0f51
Expected Behavior
Change Service.type to other type other than 'ClusterIP' can take effect
Actual Behavior
Only default value 'ClusterIP' take effect
Steps to Reproduce the Problem
Specifications
Recommend fix:
Or delete this value from documentation.
The text was updated successfully, but these errors were encountered: