crossplane / crossplane/provider-template
Example/documentation how to migrate provider to v2 with backward compatibility for cluster resources
- Dominant language
- Go
- Stars
- 171
- Forks
- 99
- Avg merge
- 11h 21m
- Merged PRs (30d)
- 2
Description
Hi,
I have question about the migration to v2. I'm developing rabbitmq provider which using this template but the upgraded template has only namespaced resources.
Could you provide examples (or at least some guidelines) how to keep backward compatibility and how older clustered resources should be handles using v2 api?
Most of the providers are generated with upjet but I haven't seen any guidelines or migration guide for providers which are based on this template.
I spend quite a lot of time with trying to understand the migration v2 changes commit in this repo but still has some question related how to handle the clustered objects (as there is no example with that path).
Should old CRDs use still v1 api or there is some special way of handling it? The `xpv1.ResourceSpec` types cannot be used with v2 apis (I mean the controller logic which is provided for example type) so I just wondering what's the recommended way to handle it smootly and support both versions. Should old clustered object still use v1 api or what's the solution for that issue.
Thanks for any advice.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.