📖 Add v1beta2 doc updates + migration doc for v1beta1 to v1beta2#3098
📖 Add v1beta2 doc updates + migration doc for v1beta1 to v1beta2#3098bnallapeta wants to merge 3 commits intokubernetes-sigs:mainfrom
Conversation
Signed-off-by: Bharath Nallapeta <nr.bharath97@gmail.com>
k8s-ci-robot
added
the
do-not-merge/hold
✅ Deploy Preview for kubernetes-sigs-cluster-api-openstack ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
k8s-ci-robot
added
size/L
|
The .lycheeignore file excludes 3 external URLs that are valid but reject automated link checkers (docs.openstack.org returns 403, freedesktop.org returns 418). All 3 URLs resolve successfully with a browser. These were pre-existing links, the changes only triggered the check by modifying the files they're in. |
bnallapeta
force-pushed
the
migration_docs
branch
from
1cad964 to
f82f487
Compare
Signed-off-by: Bharath Nallapeta <nr.bharath97@gmail.com>
bnallapeta
force-pushed
the
migration_docs
branch
from
f82f487 to
6f2d968
Compare
Signed-off-by: Bharath Nallapeta <nr.bharath97@gmail.com>
bnallapeta
force-pushed
the
migration_docs
branch
from
225485e to
d2e2d17
Compare
nikParasyr
left a comment
nikParasyr
left a comment
There was a problem hiding this comment.
/lgtm
Couple of nits/comments but not blockers
|
|
||
| **For most users, no action is required.** The conversion webhooks handle all translation between v1beta1 and v1beta2 automatically. The changes below are relevant primarily for developers writing controllers or tooling that reads CAPO objects directly. | ||
|
|
||
| There are **no breaking changes to spec fields**. All spec fields from v1beta1 are present and unchanged in v1beta2. The breaking changes are limited to status fields and internal representations. |
There was a problem hiding this comment.
We intend to do some "cosmetic" changes to .spec, but i guess this should be updated when those changes land.
There was a problem hiding this comment.
Agreed. Perhaps once your PRs are merged, please remember to update the docs accordingly.
| |--------------|-----------------------| | ||
| | **v1beta1** | TBD (current stable) | | ||
| | **v1beta2** | TBD (current stable) | | ||
| | **v1beta1** | TBD (still served) | |
There was a problem hiding this comment.
Maybe not required in this PR but we should come up with a deprecation&removal timeline before we release
There was a problem hiding this comment.
Good point. @lentzi90 Do we have any guidance for the timelines from earlier API migrations?
k8s-ci-robot
added
the
lgtm
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: nikParasyr The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
3 participants
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Fixes #2944
TODOs:
/hold