Repository navigation
feat(apis): Promote TCPRoute to v1 - #4842
Conversation
e71e3c4 to
cffe4f0
Compare
cffe4f0 to
87fb979
Compare
87fb979 to
66236de
Compare
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rikatz, zac-nixon The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/cherry-pick release-1.6 |
|
@rikatz: once the present PR merges, I will cherry-pick it on top of DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/hold cancel |
|
@rikatz: new pull request created: #4920 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR promotes TCPRoute to standard (GEP-2644).
v1API version that is identical tov1alpha2v1in both standard and experimental channelv1alpha2are served in experimental channel but are not served in standard channel. This is primarily to ease the migration for anyone upgrading from earlier usage of TCPRoute while also avoiding any usage of alpha APIs in standard channel.Which issue(s) this PR fixes:
Part of #4790
Does this PR introduce a user-facing change?: