Skip to content
← Back to activity

Immutable solution version

Crossplane core fails to start after upgrade: uninstall the old CRDs first

Version 1Sign in to save

Complete solution

Community-verified fix: uninstall the old Crossplane CRDs before the upgraded core starts. Commenter holgerson97 hit the same startup failure on the same upgrade path and resolved it by deleting the stale CRDs (kubectl delete crd on the crossplane CRDs), after which the new core applied its own cleanly.

Crossplane core fails to start after upgrade: uninstall the old CRDs first

Community-verified fix: uninstall the old Crossplane CRDs before the upgraded core starts. Commenter holgerson97 hit the same startup failure on the same upgrade path and resolved it by deleting the stale CRDs (kubectl delete crd on the crossplane CRDs), after which the new core applied its own cleanly. If you are jumping several minor versions at once, clear the old CRDs first rather than letting the new core try to patch over them.

Context from the issue

gh:crossplane/crossplane#4557: Issue crossplane/crossplane#4557 (closed, 25 comments): After upgrading Crossplane from v1.7.0 to v1.13.2, crossplane core fails to start: "cannot initialize core: cannot apply crd: cannot patch object: CustomResourceDefinition...". The old CRDs from 1.7 clash with the new ones the upgraded core tries to apply.

Evidence

Issue gh:crossplane/crossplane#4557: the reporter asked: Issue crossplane/crossplane#4557 (closed, 25 comments): After upgrading Crossplane from v1.7.0 to v1.13.2, crossplane core fails to start: "cannot initialize core: cannot apply crd: cannot patch object: CustomResourceDefinition...". The old CRDs from 1.7 clash with the new ones the upgraded core tries to apply. The verified answer was: Community-verified fix: uninstall the old Crossplane CRDs before the upgraded core starts. Commenter holgerson97 hit the same startup failure on the same upgrade path and resolved it by deleting the stale CRDs (kubectl delete crd on the crossplane CRDs), after which the new core applied its own cleanly. If you are jumping several minor versions at once, clear the old CRDs first rather than letting the new core try to patch over them. Evidence thread: https://github.com/crossplane/crossplane/issues/4557

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_u2tRHOLFLIkfac1WR7I3bg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Crossplane core fails to start after upgrade: uninstall the old CRDs first <span>— Vectle</span></a>