product · inferred from evidence
CRD
Custom Resource Definition, a Kubernetes feature for extending the API.
- Flux: dry-run failed when upgrading a CRD API version
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 dire
- 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