The null-safe fallback helpers from #99 pass values through fromYaml, which goes over JSON and therefore parses every number as float64. Go's "%v" switches float64 to exponential notation from about 1e6 upwards, so a bare byte count like 1048576 reached multiplyQuantity as "1.048576e+06" and the suffix check aborted the render: unsupported resource quantity suffix "e+06" in "1.048576e+06" The second "%v" — the output of a non-integer product — never reaches that check, so it produced an invalid quantity without any abort. In this chart that value is caught one step later by NOTES.txt, which feeds the computed memory limit back into multiplyQuantity: the Deployment still carried memory: "1.4999985e+06" and the error pointed at NOTES.txt:54 instead of the real cause. Both places now go through a new formatNumber helper, which forces decimal notation via "%.10f" and trims the padded zeros again; strings such as "512Mi" pass through untouched. This is the canonical fix from #157, taken over verbatim with this chart's prefix, because multiplyQuantity is the same copy in every chart. Chart defaults render unchanged. Patch bump: bug fix only, no behavior and no values-schema change; appVersion stays.
10 lines
229 B
YAML
10 lines
229 B
YAML
apiVersion: v2
|
|
name: apache-tika
|
|
description: A Helm chart to deploy Apache Tika on Kubernetes
|
|
icon: https://www.apache.org/logos/res/tika/default.png
|
|
|
|
type: application
|
|
|
|
version: 10.0.1+up3.3.1.0.full
|
|
appVersion: "3.3.1.0-full"
|