Skip to content

Helm values.yaml validation with sub-chart and null isn't working correctly #12417

@sumo-drosiek

Description

@sumo-drosiek

I have experienced linting error, while I'm using null as value for subchart. I would expect that validation will be made after fallback to default sub-chart value

Error:

 helm install sumo1695302553314 sumologicdev/sumologic -f values.yaml --devel --version 3.14.0-46-g543a433e2f             
WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /home/drosiek/.kube/config
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /home/drosiek/.kube/config
Error: INSTALLATION FAILED: values don't meet the specifications of the schema(s) in the following chart(s):
opentelemetry-operator:
- manager: env is required

Chart.yaml

values.yaml:

opentelemetry-operator:
  manager:
    env: null

Output of helm version:

version.BuildInfo{Version:"v3.12.0", GitCommit:"c9f554d75773799f72ceef38c51210f1842a1dea", GitTreeState:"clean", GoVersion:"go1.20.4"}

Output of kubectl version:

Client Version: v1.28.2
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.23.17-2+40cc20cc310518
WARNING: version difference between client (1.28) and server (1.23) exceeds the supported minor version skew of +/-1

Cloud Provider/Platform (AKS, GKE, Minikube etc.):
microk8s

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions