jklein
db00198c6b
Part of #43 — templates/NOTES.txt. The rule from the approved plan was that a NOTES.txt repeating the values is worthless, so this one prints what an operator would otherwise look up in the templates: the rendered URL (or the port-forward command when the Ingress is off, plus the reason ingress.domain stays required — it is CORE_DEFAULT_DOMAIN), the two op:// refs together with the exact field names the 1Password items must carry ("connection-url" and "server-secret", because the operator names the Secret keys after the item's fields), and the traps of this chart: the setup page hands the super administrator to whoever reaches the URL first, migrations run inside the startup probe's window (computed from the effective probe values), a database outage leaves the pod running and NotReady because liveness deliberately uses "/", the upload ceiling that actually bites is the Ingress annotation and not the app's fixed 500mb, /tmp is an emptyDir counted against the ephemeral-storage limit (computed) so an oversized upload evicts the pod, and the uploads PVC is an ordinary release resource that "helm uninstall" deletes. Conditional sections cover scaleDown / replicas: 0, more than one replica against the single ReadWriteOnce claim, and a set zipline.env. No domain is baked into the chart; every host is rendered from the values, examples use example.com. Part of #157 — multiplyQuantity. The null-safe fallbacks pass values through fromYaml, which parses every number as float64, and Go's "%v" switches float64 to exponential notation from about 1e6 upwards: a bare "1048576" arrived as "1.048576e+06" and the render aborted on the suffix check. This is the canonical correction agreed for all charts, taken over verbatim with this chart's prefix — the input and the non-integer product now go through a formatNumber helper, and the toYaml/fromYaml round trip is not touched, since it is not the cause. Measured against ci/zipline/test-values.yaml on the chart's only resources path, zipline.resources: before, both requests.memory=1048576 and requests.ephemeralStorage=1048576 aborted with unsupported resource quantity suffix "e+06" in "1.048576e+06" after, they render with the limits "3145728", while the 65536 fallback probe still yields 196608 unchanged. Rendered manifests are byte-identical to the previous version for the default values.
26 lines
1.2 KiB
YAML
26 lines
1.2 KiB
YAML
apiVersion: v2
|
|
name: zipline
|
|
description: A Helm chart for deploying Zipline on Kubernetes
|
|
icon: https://raw.githubusercontent.com/diced/zipline/trunk/public/favicon-128x128.png
|
|
|
|
# A chart can be either an 'application' or a 'library' chart.
|
|
#
|
|
# Application charts are a collection of templates that can be packaged into versioned archives
|
|
# to be deployed.
|
|
#
|
|
# Library charts provide useful utilities or functions for the chart developer. They're included as
|
|
# a dependency of application charts to inject those utilities and functions into the rendering
|
|
# pipeline. Library charts do not define any templates and therefore cannot be deployed.
|
|
type: application
|
|
|
|
# This is the chart version. This version number should be incremented each time you make changes
|
|
# to the chart and its templates, including the app version.
|
|
# Versions are expected to follow Semantic Versioning (https://semver.org/)
|
|
version: 7.1.0+up4.7.0
|
|
|
|
# This is the version number of the application being deployed. This version number should be
|
|
# incremented each time you make changes to the application. Versions are not expected to
|
|
# follow Semantic Versioning. They should reflect the version the application is using.
|
|
# It is recommended to use it with quotes.
|
|
appVersion: 4.7.0
|