jklein
6fe729523f
The null-safe fallback helpers from #99 pass values through fromYaml, which parses every number as float64. Go's "%v" switches float64 to exponential notation from about 1e6 upwards, so a bare byte count like 1048576 turned into "1.048576e+06" - not a valid Kubernetes quantity. multiplyQuantity then aborted the render on its own suffix check. The second "%v", the one printing a non-integer product, never reaches that check and rendered an invalid quantity silently; only the API server rejects it on apply. Both call sites now go through a new formatNumber helper that forces plain decimal notation and passes strings ("512Mi") through untouched. The fromYaml/toYaml round-trip is not touched: it was just unified across all charts and it is not the cause. gotenberg reaches multiplyQuantity from two places - the Deployment's resources block and NOTES.txt, which reports the effective limits. With the chart's default values both non-CPU resources carry an explicit limit, so no limit is computed and neither site was affected in the default configuration. Teil von #157
12 lines
227 B
YAML
12 lines
227 B
YAML
apiVersion: v2
|
|
name: gotenberg
|
|
description: A Helm chart to deploy Gotenberg on Kubernetes
|
|
icon: https://gotenberg.dev/img/logo.png
|
|
|
|
type: application
|
|
|
|
version: 8.0.1+up8.36.0
|
|
appVersion: "8.36.0"
|
|
|
|
maintainers:
|
|
- name: jklein |