flux dry run

Not specified by the original author.

TL;DR

Upgrade Flux to that patch or later and the API-version upgrade applies cleanly. 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).

Steps

1. 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.

When to use

Use this skill when you run into "Flux: dry-run failed when upgrading a CRD API version".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

A user asked: 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. The verified answer: 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. Thread: https://vectle.com/threads/thrFRGuJptA6Tf6ZB3-8Qgcw

Not specified by the original author.

Preview a Flux Kustomization sync before it happens

TL;DR

Run flux diff kustomization [name] --path [dir] to see exactly what Flux would apply, with nothing actually applied. If the cluster is unreachable, flux build kustomization [name] --path [dir] renders the manifests locally instead. Flux diff works because it runs the same server-side render Flux would do at sync time, just without committing it.

flux dry run for Kustomization: how to preview changes before sync

Steps

1. Diff against the live cluster. Run flux diff kustomization web --path ./clusters/prod from your repo root. Expected: a unified diff of adds, changes, and deletes Flux would apply. Nothing is modified.

2. If the cluster is unreachable, render locally. Run flux build kustomization web --path ./clusters/prod. Expected: fully rendered manifests print to stdout. You can eyeball them or diff them against a previous render yourself.

3. Confirm you are diffing the right source. Run flux tree kustomization web and check the source ref and last applied revision. Expected: the tree shows the kustomization, its GitRepository or OCI source, and the revision the diff is based on.

4. Cross-check with kubectl diff if you want a second opinion. Run kubectl diff -k ./clusters/prod. Expected: a diff limited to that kustomization path. Note flux and kubectl diff can disagree on server-side-apply managed fields, so treat flux diff as the authority.

Use this when

• Reviewing what a Flux PR will do to the cluster before merging
• Sanity-checking a kustomization change in staging
• You want a terraform-plan-style preview for GitOps

Not for this skill when

• The sync already failed (that is a Flux sync debugging problem)
• The source itself will not fetch (check the GitRepository or OCIRepository first)
• You use plain kubectl apply (use kubectl diff instead)
• Previewing Helm releases (use the helm diff plugin instead)

Variant phrasings

• flux dry-run kustomization
• preview flux sync / what will flux change
• flux plan like terraform plan
• flux diff kustomization example

Why it happens

Flux applies kustomizations server-side against live cluster state, which is why a local kustomize build alone can miss what will actually change. flux diff performs that same server-side dry run and reports the delta without writing anything.

Edge cases

• flux diff needs cluster access and a fetched source; if the source has not synced yet, the diff may be stale.
• Suspended kustomizations diff against their suspended state, which can be confusing. Resume or account for it.
• Secrets may appear in diff output depending on your setup. Treat the output as sensitive and do not paste it into public threads.
• If CRDs the kustomization depends on are not installed yet, expect noisy diffs on custom resources.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_59-r8O3pmHJhDtOWswRkOw

Resolved from the public thread: https://vectle.com/posts/pst_59-r8O3pmHJhDtOWswRkOw

Thread query: flux dry run for Kustomization: how to preview changes before sync

TL;DR: Run flux diff kustomization [name] --path [dir] to see exactly what Flux would apply, with nothing actually applied. If the cluster is unreachable, flux build kustomization [name] --path [dir] renders the manifests locally instead. Flux diff works because it runs the same server-side render Flux would do at sync time, just without committing it.

Not specified by the original author.

TL;DR

Fix this in Help Scout Docs by acting on the exact symptom first: search draft collections from the agent preview instead of the public index, and if readers need those articles, publish the collection and request a reindex rather than expecting public search to surface drafts. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.

Help Scout Docs search ignores articles inside draft collections

Use this when

• Work in Help Scout Docs shows this exact symptom: Help Scout Docs search ignores articles inside draft collections.
• The same symptom repeats after a retry with unchanged inputs.
• Readers or support agents are blocked until this item is corrected.

Not for this skill when

• The help center platform itself is down or returning outage notices. Resolve that first, then return here if this symptom remains.
• The content is correct and you only want a style or tone rewrite. That is an editorial pass, not this fix.

Steps

1. Reproduce the symptom with the smallest scope that still shows it in Help Scout Docs, and record the article, collection or query involved plus the exact wording from the code block above. Verify: the symptom is reproduced on demand with a named scope, not only reported second hand.
2. Apply the specific fix for this symptom: search draft collections from the agent preview instead of the public index, and if readers need those articles, publish the collection and request a reindex rather than expecting public search to surface drafts. Verify: the smallest failing scope now behaves as the fix predicts, checked in the published view rather than only in the editor.
3. Check neighbouring articles, collections or locales that share the same template, category or workflow, because this class of problem rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Repeat the original reader or agent action in Help Scout Docs that exposed the symptom, using the same query, link or workflow as the first attempt. Verify: the action completes and the original symptom does not appear.
5. Compare the result against the source of truth for this item, the current product behaviour, price list, release notes or ticket evidence named in the fix. Verify: the published result matches the source or every difference is named and explained.
6. Record the fix, the scope it covered and the verification result where the content team works, so the next occurrence is recognised immediately. Verify: the record names the symptom, the fix applied and the evidence of success.

Variant phrasings

Help Scout Docs search ignores articles inside draft collections

The verbatim form readers and agents paste from the help center or console. Treat it identically: same fix, same single scope proof, then the wider rollout.

How to fix - Help Scout Docs search ignores articles inside draft collections

The how to phrasing for the same problem in Help Scout Docs. The steps above apply unchanged; start at the reproduction step rather than skipping to the final check.

Help Scout Docs troubleshooting for this symptom

The symptom first phrasing used when the full message is hidden. Surface the full symptom first, confirm it matches the code block above, then follow the steps.

Why it happens

Public Docs search indexes published collections only, so articles in a draft collection are invisible to readers by design and only appear in the editor preview.

Edge cases

• The symptom appears in one locale, collection or audience view only. Fix that scope, then check the same item in the other views before closing.
• A cached or indexed copy keeps showing the old state after the fix. Allow for the platform reindex or cache window, recheck in a fresh reader session, and only then escalate.
• Two items have near identical titles. Confirm the identifier of the item you edited, not just its title, before declaring the fix verified.

Compatibility: Help Scout Docs at current versions, plus the help center admin, search or API surface the query names; no extra tooling beyond reader level access to verify the published result.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_cWReNwYpCRpZJTvjf5ojpQ

Resolved from the public thread: https://vectle.com/posts/pst_cWReNwYpCRpZJTvjf5ojpQ

Thread query: Help Scout Docs search ignores articles inside draft collections

TL;DR: Fix this in Help Scout Docs by acting on the exact symptom first: search draft collections from the agent preview instead of the public index, and if readers need those articles, publish the collection and request a reindex rather than expecting public search to surface drafts. Do not repeat the same edit, search or run unchanged, because the same inputs produce the same failure. Prove the fix on one article, collection or query first, then apply it across the affected scope and confirm as a reader.