Skip to content
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.

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

Upgrade CAPA to v2.3.0 but comment out CRD upgrade so existing clusters reconcile fine without having the newly-required subnet id field yet #192

Merged
merged 1 commit into from
Nov 30, 2023

Conversation

AndiDog
Copy link
Contributor

@AndiDog AndiDog commented Nov 28, 2023

Towards giantswarm/roadmap#2870, namely the first step of the suggested migration.

Note that since the old CRDs are used here, avoiding that the subnet id field is required for now, the make verify CI job is failing. That must be accepted until step two (update to actual, latest CRDs which make the field required).

See related cluster app changes:

Checklist

  • Update changelog in CHANGELOG.md.

…rs reconcile fine without having the newly-required subent `id` field yet
@AndiDog AndiDog merged commit 96bc5c5 into master Nov 30, 2023
3 of 4 checks passed
@AndiDog AndiDog deleted the capa-v2.3.0-with-old-crds branch November 30, 2023 07:54
@AndiDog AndiDog changed the title Upgrade CAPA to v2.3.0 but comment out CRD upgrade so existing clusters reconcile fine without having the newly-required subent id field yet Upgrade CAPA to v2.3.0 but comment out CRD upgrade so existing clusters reconcile fine without having the newly-required subnet id field yet Nov 30, 2023
@AndiDog AndiDog mentioned this pull request Nov 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants