Jared Watts

That's definitely unexpected 🤔 - can you include the full output of `kubectl get crd locks.pkg.crossplane.io -o yaml`?

By the way, I was able to upgrade a control plane just now from 1.18.2 --> 1.19.0 --> 1.20.0 without issues, so this scenario isn't completely borked at least 🙏

Oh and please amend any commits you make to include the DCO sign-off. Info about that can be found in https://github.com/crossplane/crossplane/tree/main/contributing#certificate-of-origin

Thanks for reporting this @malins! Looks like that version is overridden later on with a `replace` statement at the end of the `go.mod` file: https://github.com/crossplane-contrib/provider-kubernetes/blob/main/go.mod#L109 * What version of `go`...

A reminder for this very proposal came up again this week with https://github.com/crossplane/crossplane/issues/6148 😞

Thanks again @chlunde for bringing this up - it's bitten us too many times now. Let's get this documented during the v1.19 milestone and put it into practice for any...

Just dropping some thoughts from @negz here for future reference, with light edits for context: > The general problem here seems to be an XR and a provider fighting over...

breadcrumbs to https://github.com/crossplane/crossplane/issues/5636 which looks related (similar error in `make run`)

Good point @cjuega, thanks for calling that out! Looks like we mention this general problem in the green tip box in https://docs.crossplane.io/v1.20/concepts/providers/#runtime-configuration: > Since DeploymentRuntimeConfig uses the same schema as...

This scenario will probably be pretty common for folks in v2 that are excited to compose arbitrary resources. They also need to take steps to grant Crossplane permissions to these...