Api deprecation blogpost: Include minimum kube version for ingress from networking apigroup #15740
Conversation
…om networking apigroup
k8s-ci-robot
added
cncf-cla: yes
|
Deploy preview for kubernetes-io-master-staging ready! Built with commit df1d1c8 https://deploy-preview-15740--kubernetes-io-master-staging.netlify.com |
| @@ -34,8 +34,8 @@ from **extensions/v1beta1**, **apps/v1beta1**, or **apps/v1beta2** in **v1.16**. | |||
| * Migrate to the apps/v1 API, available since v1.9. Existing persisted data | |||
| can be retrieved/updated via the apps/v1 API. | |||
| * Ingress: will no longer be served from **extensions/v1beta1** in **v1.18**. | |||
| * Migrate to the networking.k8s.io/v1beta1 API. Existing persisted data can be | |||
| retrieved/updated via the networking.k8s.io/v1beta1 API. | |||
| * Migrate to the networking.k8s.io/v1beta1 API, serving Ingress since v1.14. | |||
There was a problem hiding this comment.
Nitpick: I recommend saying "available since v1.14"
There was a problem hiding this comment.
I deliberately put it like that because the networking.k8s.io apigroup is available since 1.8 and Ingress itself since 1.1. The only thing changed with 1.14 is that you can now get the Ingress kind via the networking.k8s.io apigroup.
There was a problem hiding this comment.
Gotcha! Thank you, @alvaroaleman 👍🏼
|
/lgtm |
k8s-ci-robot
added
the
lgtm
|
Thank you, @alvaroaleman! Looks good to me from a technical perspective. /lgtm |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kbarnard10 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
the
approved
…om networking apigroup (kubernetes#15740)
…om networking apigroup (kubernetes#15740)
Ingress lacks the info what the minimum required Kube version is, its included for all other resources mentioned.
/assign @vllry