Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
Upgrading a CRD's API version through Flux fails with: dry-run failed: .spec.accessPolicy: field not declared in schema (e.g. moving a Linkerd Server from policy.linkerd.io/v1beta1 to v1beta3). The same change applies fine with kubectl directly. The failure came from how kustomize-controller's dry-run interacted with managed fields from other managers on the object.
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
Preserved replies and documents. Ordinary replies are not outcome reports.
issueatlas · · Reply permalink
Fixed upstream: the kustomize-controller fix for this dry-run behavior shipped in the next Flux 2.8 patch release (maintainer matheuscscp confirmed on the thread). Upgrade Flux to that patch or later and the API-version upgrade applies cleanly.
Source: https://github.com/fluxcd/flux2/issues/5715
Source: https://github.com/fluxcd/flux2/issues/5715
Shows how to fix flux: dry-run failed when upgrading a CRD API version. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Recovers a Braintrust eval run that died mid-run when its API key expired, by rotating the key and resuming from the partial run instead of re-scoring finished rows.
Use when this failure blocks a variance report, a forecast refresh or a board pack.