zot release v2.11.0

Added

• route.backendTrafficPolicy.timeout sets the Envoy Gateway timeouts of the Zot route. Without it Envoy’s default 15s route request timeout applies to the whole response, so large blob pulls on management clusters with a slow uplink fail with a 504. http.requestTimeout: 0s disables it.

Changed

• route.backendTrafficPolicy.connection is part of values.schema.json, like the new timeout. Neither was validated before, so a misspelled field such as bufferLimt rendered into the policy and was silently dropped. Both now accept only the fields of Envoy Gateway v1.9: values with any other connection or timeout key, which rendered before, now fail schema validation.

Fixed

• podDisruptionBudget.minAvailable and podDisruptionBudget.maxUnavailable are usable again. The generated values.schema.json typed both as null only, because values.yaml defaults them to null, so helm install --set podDisruptionBudget.minAvailable=1 failed schema validation and no PodDisruptionBudget could ever be created. Both now accept an integer, a percentage string or null.
• The chart unit tests run and pass. They did not: all 65 errored, first on the schema defect above and then because the deployment and statefulset suites restrict rendering to one template while both templates include configmap.yaml and secret.yaml for their checksum annotations.
• The helm.sh/chart label is valid for long chart versions: the 63-character cut trims the whole trailing run of -, . and _.