Changelog
[1.32.1]
CHANGES:
- added Gateway API objects in version 1.2.0-experimental as main object types to HULL:
backendlbpolicy
,backendtlspolicy
,gatewayclass
,gateway
,grpcroute
,httproute
,referencegrant
,tcproute
,tlsroute
andudproute
. This should make it more comfortable to use them opposed to specifying them using the genericcustomresource
object type. Thanks to suggestion from ievgenii-shepeliuk made here - introducing
sources
feature for pods (pod
level in the workload specifications) and containers (initContainers
andcontainers
levels in the workload specifications). Usingsouces
enables global defaulting of pod and container properties and flexible sharing plus stacking of sets of properties for both pods and containers. Potential usages range from globally enforcing workload security settings, specifying shared minimum or special resource requirements or harmonization of all pods and containers in a chart. See the chart design guide for details. This also closes issues Add sharedContainers feature and Default security settings. - added configurable multi-pass rendering of HULL transformations. This enables forward referencing of values in the YAML tree which was previously not possible. For example, using only a single HULL transformation rendering pass, a field
.Values.hull.config.specific.field_a: _HT*hull.config.specific.field_b
, where_HT*hull.config.specific.field_b: _HT*hull.config.specific.field_c
, will resolvefield_a
to literal string_HT*hull.config.specific.field_c
. This is the case because at the time whenfield_a
is resolved the value offield_b
is not yet resolved due to the alphanumeric order of HULL transformation processing. With the new multi-pass default ofhull.config.general.render: 3
, thefield_a: _HT*hull.config.specific.field_c
value is fully resolved to the referenced value of_HT*hull.config.specific.field_c
in the second pass.