@AGENTS.md @CONTRIBUTING.md
- Values changes: show
--setflags or a patch values file overlay, not edits tovalues.yamldirectly, unless there is a change with the default value that should be reflected invalues.yaml(e.g. a new component'senabledflag) - New templates: show the complete file including the
{{- if .Values.<component>.enabled }}guard andinclude "mlrun-ce.common.labels"call - Service references within templates: use
{{ .Release.Namespace }}, never hardcode namespace strings - After any
requirements.yamlchange: remind the user to runmake helm-update-dependenciesand commitrequirements.lock - Please make sure to update all values files in
charts/mlrun-ce/if your change affects the default installation — e.g. if you add a new component with anenabledflag, add it tovalues.yamland all three install-mode values files (admin_installation_values.yaml,non_admin_installation_values.yaml,non_admin_cluster_ip_installation_values.yaml) with the appropriate default value - Update README docs if your change adds a new component, changes component version or changes the installation process.