v3.1.1

What's Changed

• feat: support revisionHistoryLimit on Deployments and StatefulSets by @edvegas in #121
• feat: add release v3.1.1 by @Gekter in #123
• feat: support revisionHistoryLimit on DaemonSet by @SachkovDM

Added

• added revisionHistoryLimit support for deployments, statefulSets, and daemonSets, including deploymentsGeneral, statefulSetsGeneral, and daemonSetsGeneral fallbacks. An explicitly set 0 is honoured; when unset, the field is omitted and the Kubernetes default (10) applies.

Fixed

• fixed replicas: 0 on deployments and statefulSets being rendered as 1: an explicit 0 was treated as an unset value by default. An explicitly set 0 is now honoured; the default of 1 still applies when replicas is omitted (#119).

Changed

• behavior change: generic.usePredefinedAffinity default changed from true to false: workloads without an explicit affinity no longer get generated affinity presets, so no affinity block is rendered unless requested. Set generic.usePredefinedAffinity: true (or per workload kind, e.g. deploymentsGeneral.usePredefinedAffinity: true) to keep the previous behavior (#21).
• podAffinityPreset default changed from soft to "": the generated pod affinity and pod anti-affinity presets contradicted each other and cancelled out while adding scheduler overhead. With presets enabled, only the soft pod anti-affinity is generated by default now (#21).
• generated affinity no longer renders empty preset sub-blocks (nodeAffinity: {} and alike); when all presets are empty the affinity block is omitted entirely (#21).
• regenerated Chart.lock to match the dependencies declared in Chart.yaml: nuc-common 1.0.5, nuc-native-gateway 1.0.6, nuc-external-secrets 1.1.0, and added lock entries for nuc-argocd, nuc-keycloak-operator, and nuc-strimzi-kafka-operator.

Testing

• added unit suites tests/units/replicas_test.yaml, tests/units/affinity_presets_test.yaml, and tests/units/revision_history_limit_test.yaml covering the changes above.

Full Changelog: v3.1.0...v3.1.1