/sig aws
/sig cloud-provider
/assign @mcrute @d-nishi
@d-nishi your copy/pasta from #630 has the same descriptor
/milestone v1.13
/stage alpha
@kacole2 - updated. Thanks for the catch.
Hi @d-nishi and @mcrute, I'm Enhancements Shadow for 1.13. Could you please update the release team with the progression of this enhancement for the 1.13 release?
Code slush begins on 11/9 and code freeze is 11/15.
Thank you!
@ameukam the current state of this is:
Do we need to show anything else?
@mcrute Thank you for the update! Please can you add the links for the CI Signal and the Docs ?
/kind feature
The CI signal is pending kubernetes/test-infra#10151
The docs are pending kubernetes/cloud-provider-aws#21 which is WIP
@d-nishi - Hello, enhancements lead for 1.14 here - it looks like this issue is targeting beta for 1.14 can you confirm if that is still what is planned? Thanks.
@claurence yes, this is targeting 1.14 for beta
/remove-milestone v1.13
/milestone v1.14
@ameukam: You must be a member of the kubernetes/kubernetes-milestone-maintainers github team to set the milestone.
In response to this:
/remove-milestone v1.13
/milestone v1.14
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/test-infra repository.
@mcrute thanks! Any open PRs we should track for 1.14?
FYI put together the boiler plate for this KEP here https://github.com/kubernetes/enhancements/pull/735
@d-nish @mcrute - The KEP for this issue is marked as "provisional" what additional work is needed for this to be "implementable"
Additionally are there any open PRs in k/k that are needed for 1.14? Code freeze is March 7th and all open PRs need to be merged then.
@claurence we're going to push this out to 1.15 I'll work on updating the KEP for that release
Thank you for the update!
Hello, I'm the Enhancement Lead for 1.15. Is this feature going to be graduating alpha/beta/stable stages in 1.15? Please let me know so it can be tracked properly and added to the spreadsheet.
Once coding begins, please list all relevant k/k PRs in this issue so they can be tracked properly.
@kacole2 we are going to try to push this to beta for 1.15 but I'm going to open a fresh issue with more details and close this one.
/close
@mcrute: Closing this issue.
In response to this:
@kacole2 we are going to try to push this to beta for 1.15 but I'm going to open a fresh issue with more details and close this one.
/close
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/test-infra repository.