Skip to content

Guide for updating v1 -> v2 #976

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 4 commits into from
Aug 15, 2025
Merged

Guide for updating v1 -> v2 #976

merged 4 commits into from
Aug 15, 2025
+784 −14

Conversation

negz
Copy link
Member

@negz negz commented Aug 14, 2025 •
edited
Loading

The key points I want to get across with this guide is:

  1. Who can upgrade (what breaking changes we made)
  2. That there's no tooling to automate migration yet
  3. That you can upgrade and start using v2 features anyway

@netlify Netlify
Copy link

netlify bot commented Aug 14, 2025 •
edited
Loading

✅ Deploy Preview for crossplane ready!

Name Link
🔨 Latest commit 5e5a548
🔍 Latest deploy log https://app.netlify.com/projects/crossplane/deploys/689f9c082d7be30008451dc0
😎 Deploy Preview https://deploy-preview-976--crossplane.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse		 1 paths audited
Performance: 96 (🟢 up 3 from production)
Accessibility: 90 (🔴 down 2 from production)
Best Practices: 92 (no change from production)
SEO: 100 (no change from production)
PWA: 70 (no change from production)
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@negz negz force-pushed the guidance branch 3 times, most recently from 89ecd9c to 57cfbd2 Compare August 14, 2025 22:42
@jbw976 jbw976 mentioned this pull request Aug 14, 2025
Open
@negz negz force-pushed the guidance branch 3 times, most recently from 7398aed to 913662d Compare August 14, 2025 23:30
@negz
Guide for updating v1 -> v2
5255979 
The key point I want to get across with this guide is:

1. Who can upgrade (what breaking changes we made)
2. That there's no tooling to automate migration yet
3. That you can upgrade and start using v2 features anyway

Signed-off-by: Nic Cope <[email protected]>
@negz negz marked this pull request as ready for review August 15, 2025 00:04
@negz negz changed the title WIP: Guide for updating v1 -> v2 Guide for updating v1 -> v2 Aug 15, 2025
@stevendborrelli
Copy link
Contributor

stevendborrelli commented Aug 15, 2025 •
edited
Loading

I don't know if it belongs here, but we should note in upjet providers we have a lot of v1beta2 APIs due to API changes and differences in handling single-item lists. In the new v2 namespaced providers, all APIs are v1beta1.

In the v2 provider the legacy cluster-scoped MRs still retain the v1beta1/v1beta2 APIs and the automated conversion web hooks, but the v2 namespace-scoped provider is v1beta1 only that matches the newest API of the legacy provider.

For example, the AWS Glue catalog table has a v1beta2 API that is now been replaced with a v1beta1 API in the 2.0.0 provider:

https://marketplace.upbound.io/providers/upbound/provider-aws-glue/v2.0.0/resources/glue.aws.m.upbound.io/CatalogTable/v1beta1

https://marketplace.upbound.io/providers/upbound/provider-aws-glue/v1.23.2/resources/glue.aws.upbound.io/CatalogTable/v1beta2

@negz
Copy link
Member Author

negz commented Aug 15, 2025

@jbw976 @stevendborrelli I've updated this to address the version change as well. PTAL. I'd love to get this merged ASAP.

@negz negz merged commit 3b8bad4 into crossplane:master Aug 15, 2025
7 checks passed
jbw976
jbw976 reviewed Aug 15, 2025
View reviewed changes
content/master/guides/upgrade-to-crossplane-v2.md

To use v2 namespaced managed resources in compositions:

1. **Update the API group** from `.crossplane.io` to `.m.crossplane.io`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will this possibly result in the external resource being deleted? i.e. we're changing the composed resource to a new type, so will any XR that uses this composition basically stop including the old cluster scoped one in their desired resources, resulting in it being deleted? 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jbw976 jbw976 jbw976 left review comments

@jeanduplessis jeanduplessis jeanduplessis approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@negz @stevendborrelli @jeanduplessis @jbw976