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
Doc:fix networking.k8s.io/v1beta1 for ingress #22968
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is just the output of a command so looks good to me, we don't really have to worry about K8s version in there.
Not a blocker, but it would be nice if you could add a bit more context to your commit description, though (e.g. why the change, what version of Kubernetes introduced the new API versioning).
Thanks!
Commit 7efaef0e5de5153b0ebe8c0e984262b0cc048d3c does not contain "Signed-off-by". Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/development/contributing_guide/#developer-s-certificate-of-origin |
"Ingress in the extensions/v1beta1 API version will no longer be served Migrate to use the networking.k8s.io/v1beta1 API version, available since v1.14. Existing persisted data can be retrieved/updated via the new version." https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/ Signed-off-by: yulng <wei.yang@daocloud.io>
ok,updated the commit with version description |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perfect, thank you!
Signed-off-by: yulng wei.yang@daocloud.io
Update document Ingress to networking.k8s.io/v1beta1
According to the following document:
https://kubernetes.io/blog/2019/07/18/api-deprecations-in-1-16/