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

Schedule APIs for deprecation/removal #660

Closed
joeduffy opened this issue Jul 27, 2019 · 1 comment · Fixed by #779
Closed

Schedule APIs for deprecation/removal #660

joeduffy opened this issue Jul 27, 2019 · 1 comment · Fixed by #779
Assignees

Comments

@joeduffy
Copy link
Member

From time to time, APIs are deprecated and then eventually removed. For example, coming soon: https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/. I don't believe we do anything special for such APIs today, however it would be nice to use language-level deprecation annotations to warn users in advance, before they finally go missing due to actual removal of support. I'm unsure whether this can be data-driven based on OpenAPI metadata, however clearly that would be ideal.

@lblackstone
Copy link
Member

Unfortunately it doesn't look like the OpenAPI spec includes the info we'd need to do this automatically. It is fairly uncommon for k8s to remove apiVersions, so we could add these notices in manually if it's important.

That said, I'm now wondering if we'll need to do further work in the provider to make sure that existing resources can migrate smoothly. Opened #671 to track that investigation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants