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

Return ReferencePolicy CRD, deprecated, for v0.5.0 #1201

Closed
youngnick opened this issue Jun 10, 2022 · 1 comment · Fixed by #1205
Closed

Return ReferencePolicy CRD, deprecated, for v0.5.0 #1201

youngnick opened this issue Jun 10, 2022 · 1 comment · Fixed by #1205
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Milestone

Comments

@youngnick
Copy link
Contributor

youngnick commented Jun 10, 2022

To make migration easier, we should deprecate the v1alpha2 ReferencePolicy resource in v0.5.0, rather than removing it.

This means we'll need to add the types and CRD back, and figure out how to get the deprecation field and warning set on the generated CRD object. (This will need to use https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning/#version-deprecation).

ReferencePolicy will then be removed in v0.6.0.

@youngnick youngnick added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 10, 2022
@youngnick youngnick added this to the v0.5.0 milestone Jun 10, 2022
@shaneutt shaneutt removed their assignment Jun 13, 2022
@robscott
Copy link
Member

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants