We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
The text was updated successfully, but these errors were encountered:
/assign
Sorry, something went wrong.
robscott
Successfully merging a pull request may close this issue.
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.
The text was updated successfully, but these errors were encountered: