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.

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

Add v1alpha4 to v1beta1 conversions #2781

Closed
Tracked by #2778
randomvariable opened this issue Sep 21, 2021 · 6 comments · Fixed by #2820
Closed
Tracked by #2778

Add v1alpha4 to v1beta1 conversions #2781

randomvariable opened this issue Sep 21, 2021 · 6 comments · Fixed by #2820
Assignees
@shivi28
Labels
area/api Issues or PRs related to the APIs kind/feature Categorizes issue or PR as related to a new feature. kind/release-blocking Issues or PRs that need to be closed before the next release lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
v1.0.0

Comments

@randomvariable
Copy link
Member

randomvariable commented Sep 21, 2021 •
edited
Loading

/kind feature
/area api
/priority important-soon

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 #2792
@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. area/api Issues or PRs related to the APIs priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Sep 21, 2021
@randomvariable randomvariable mentioned this issue Sep 21, 2021
Closed
7 tasks
@Ankitasw
Copy link
Member

Do we also need to have v1alpha3 to v1beta1 upgrade e2e tests, as we have in case of v1alpha3 to v1alpha4 upgrade?

@randomvariable randomvariable mentioned this issue Sep 24, 2021
Closed
@randomvariable
Copy link
Member Author

Do we also need to have v1alpha3 to v1beta1 upgrade e2e tests, as we have in case of v1alpha3 to v1alpha4 upgrade?

Yes, have added the issue

@randomvariable randomvariable mentioned this issue Sep 24, 2021
Closed
@randomvariable
Copy link
Member Author

/milestone v0.8.0

@k8s-ci-robot k8s-ci-robot added this to the v0.8.0 milestone Sep 24, 2021
@randomvariable
Copy link
Member Author

/kind release-blocking

@k8s-ci-robot k8s-ci-robot added the kind/release-blocking Issues or PRs that need to be closed before the next release label Sep 24, 2021
@shivi28
Copy link
Contributor

shivi28 commented Sep 25, 2021

/assign @shivi28

@randomvariable
Copy link
Member Author

/lifecycle active

@k8s-ci-robot k8s-ci-robot added the lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. label Oct 4, 2021
This was referenced Oct 4, 2021
Closed
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@shivi28 shivi28

Labels
area/api Issues or PRs related to the APIs kind/feature Categorizes issue or PR as related to a new feature. kind/release-blocking Issues or PRs that need to be closed before the next release lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
v1.0.0
4 participants
@randomvariable @shivi28 @k8s-ci-robot @Ankitasw