Myasnikov DaniilandClaude Opus 4.7 5121c7b91b fix(foundationdb): relocate misplaced fields from automationOptions to spec ...

The chart nested `faultDomain`, `imageType`, `labels`, and
`minimumUptimeSecondsForBounce` inside `automationOptions`, but the
FoundationDBCluster CRD schema defines all four as direct children of
`spec`. Flux v2.7 (helm-controller v1.4.3) used permissive client-side
patch and silently dropped the unknown fields; v2.8 (helm-controller
v1.5.0) does strict Server-Side Apply and rejects:

  failed to create typed patch object: .spec.automationOptions.<field>:
  field not declared in schema

This was a latent bug from day one — none of those fields ever actually
configured anything. Moving them one level up applies the values to
where the operator looks for them.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>

2026-05-28 12:43:50 +05:00

..

_resources.tpl

Add FoundationDB configuration values for storage engine and redundancy mode, update tests, and fix workload monitor

2025-09-17 01:16:19 -05:00

backup.yaml

Initial support for FoundationDB operator

2025-09-17 01:16:09 -05:00

cluster.yaml

fix(foundationdb): relocate misplaced fields from automationOptions to spec

2026-05-28 12:43:50 +05:00

dashboard-resourcemap.yaml

Initial support for FoundationDB operator

2025-09-17 01:16:09 -05:00

role.yaml

Update Foundation DB tests and update chart to make sure they pass

2025-09-17 01:16:16 -05:00

rolebinding.yaml

Update Foundation DB tests and update chart to make sure they pass

2025-09-17 01:16:16 -05:00

serviceaccount.yaml

Update Foundation DB tests and update chart to make sure they pass

2025-09-17 01:16:16 -05:00

workloadmonitor.yaml

feat(platform): add resourcePreset labels

2026-04-17 15:04:25 +04:00