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

Add v1alpha4 to v1beta1 conversions #1253

Closed
Tracked by #1249
randomvariable opened this issue Sep 24, 2021 · 3 comments
Closed
Tracked by #1249

Add v1alpha4 to v1beta1 conversions #1253

randomvariable opened this issue Sep 24, 2021 · 3 comments
Assignees
Labels
area/api kind/release-blocking Issues or PRs that need to be closed before the next CAPV release priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone

Comments

@randomvariable
Copy link
Member

/kind release-blocking
/area api
/priority important-soon
/milestone v0.8.0

Describe the solution you'd like

For v1beta1, add conversions for v1alpha4

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

We intend to support upgrades from v1alpha3 to v1beta1, so v1alpha3 conversions should not be deleted

Depends on #1251

@k8s-ci-robot k8s-ci-robot added kind/release-blocking Issues or PRs that need to be closed before the next CAPV release area/api priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Sep 24, 2021
@randomvariable randomvariable added this to the v0.8.0 milestone Sep 24, 2021
@gab-satchi
Copy link
Member

/assign

@gab-satchi
Copy link
Member

done by #1263

/close

@k8s-ci-robot
Copy link
Contributor

@gab-satchi: Closing this issue.

In response to this:

done by #1263

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/api kind/release-blocking Issues or PRs that need to be closed before the next CAPV release priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

3 participants