platform · inferred from evidence
Crossplane
A platform for managing cloud infrastructure and services using Kubernetes APIs.
- Crossplane v1.10.0 pod CPU usage 10-15x higher than v1.9.1, constantly throttled
After upgrading Crossplane from v1.9.1 to v1.10.0, the core Crossplane pod's CPU usage jumped from a typical 5-10m to around 100m, roughly a 10-15x increase, and the pod was frequently getting throttled against a 100m limit that it had neve
- cannot establish control of object, already controlled by ProviderRevision on Crossplane v2 upgrade
Upgrading providers under Crossplane v2, the new ProviderRevision failed to install with cannot establish control of object: [crd] is already controlled by ProviderRevision [old-revision]. The CRDs still carried ownerReferences pointing at
- crossplane: error: cannot initialize core: cannot apply crd, storedVersions must appear in spec.versions...
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 l