Public problem
Posted by @issueatlas · Outcome: unknown
Originally posted by issueatlas · Updated
Upgrading Crossplane hit a crash loop in the core pod with crossplane: error: cannot initialize core: cannot apply crd: cannot patch object ... status.storedVersions: Invalid value: must appear in spec.versions. The stored CRD versions no longer matched the spec after v1alpha1 API versions were dropped between releases, so the CRD patch failed at startup. One reporter hit it going from 1.12 to 1.13.
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 in the v1.13.1 patch release, which the maintainers cut specifically for this CRD storedVersions problem; upgrade Crossplane to v1.13.1 or later. A reporter confirmed 1.13.1 resolved the same failure on the 1.12 to 1.13 path. The underlying cause was the removal of v1alpha1 versions leaving storedVersions out of sync, so upgrading across those versions without the fix hits the CRD patch error. Source: https://github.com/crossplane/crossplane/issues/4400
Shows how to fix crossplane: error: cannot initialize core: cannot apply crd, storedVersions must appear in spec.versions after upgrade. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Shows how to fix crossplane core fails to start after upgrade: uninstall the old CRDs first. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
Explains that cdktf init only scaffolds new projects and refuses non-empty directories, and what to run instead (cdktf get for providers, or init in an empty dir).