kustomize: no matches for kind in apiVersion

Not specified by the original author.

TL;DR

The manifest uses an apiVersion that does not serve that kind on your cluster: typically a removed beta (like extensions/v1beta1) after a Kubernetes upgrade. Update to the current apiVersion (for example apps/v1 for Deployments) and the build succeeds.

Error

kustomize: no matches for kind in apiVersion

Steps

1. Read the error: it names the kind and the apiVersion that failed. Expected: you know which resource is wrong.
2. Check the cluster version: deprecated APIs are removed on a schedule, so confirm what your cluster serves. Expected: the apiVersion you used is gone.
3. Update the manifest to the current apiVersion for that kind (Deployments to apps/v1, Ingresses to networking.k8s.io/v1, and so on). Expected: the kind resolves.
4. Fix the schema too: apiVersion bumps often rename fields, so validate the whole object. Expected: no follow-on validation errors.
5. Re-run the kustomize build and apply. Expected: clean build and successful apply.

When to use

• Kustomize or kubectl fails with "no matches for kind"
• After Kubernetes cluster upgrades
• Old manifests with beta apiVersions

When not to use

• Kustomize syntax or overlay merge errors (different layer)
• CRDs not installed (install the CRD first)

Tool compatibility

• Kustomize, kubectl; Kubernetes API deprecation schedule

Variant phrasings

extensions v1beta1 no longer served

Move to the GA apiVersion; the beta was removed from the API server.

no matches for kind Deployment

Use apps/v1; the old beta group no longer exists on current clusters.

Why it happens

Kubernetes removes deprecated APIs after several releases, and the API server then has no mapping for kind plus old apiVersion. Manifests that worked for years break on upgrade day, which is why the fix is always "use the current apiVersion".

Provenance

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

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

Thread query: kustomize: no matches for kind in apiVersion

TL;DR: The manifest uses an apiVersion that does not serve that kind on your cluster: typically a removed beta (like extensions/v1beta1) after a Kubernetes upgrade. Update to the current apiVersion (for example apps/v1 for Deployments) and the build succeeds.

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.

Not specified by the original author.

TL;DR

Fix this in Help center search by acting on the exact symptom first: add the old feature name as a search synonym for the new name and also mention the old name once in the renamed article intro in a formerly called note, then test the old name query until the current article ranks first. 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.

Users searching old feature name find nothing, synonyms missing

Use this when

• Work in Help center search shows this exact symptom: Users searching old feature name find nothing, synonyms missing.
• 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 center search, 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: add the old feature name as a search synonym for the new name and also mention the old name once in the renamed article intro in a formerly called note, then test the old name query until the current article ranks first. 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 center search 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

Users searching old feature name find nothing, synonyms missing

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 center search synonyms missing users searching old feature name find nothing error failure

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

Help center search 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

Renames change article wording to the new name while readers keep searching the name they learned, and without synonyms or a bridge mention the search engine has no link between the two terms.

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 center search 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_9hI5MDPUUiJN-tPldma4uw

Resolved from the public thread: https://vectle.com/posts/pst_9hI5MDPUUiJN-tPldma4uw

Thread query: help center search synonyms missing users searching old feature name find nothing error failure

TL;DR: Fix this in Help center search by acting on the exact symptom first: add the old feature name as a search synonym for the new name and also mention the old name once in the renamed article intro in a formerly called note, then test the old name query until the current article ranks first. 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.