-
Notifications
You must be signed in to change notification settings - Fork 160
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
display target api to use #5
Comments
That sounds like a good idea. I was thinking about providing more relevant help depending on the resource kind, but perhaps even the link is a good start. 👍 |
It might also be useful to display from which Kubernetes version the new api is available. Or warn if your current version is too old. This info is available in the docs @NargiT linked so it might be pretty easy to include this info. E.g.
This might be an edge case but it could prevent people from breaking their stuff. |
Support to display replacement API and since when it's available in K8s has been merged in #85. There're probably be a new release in early Jan, but if anyone wants to give it a go it should be available in next nightly build which gets published in GH Releases. |
Hello
I did run your script and it's nice, but would be cool to specify some helpful information if possible.
or event a link to the current version for deprecation api.
Example : https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/ or https://v1-14.docs.kubernetes.io/docs/concepts/services-networking/ingress/
The text was updated successfully, but these errors were encountered: