-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
aws-alb-ingress-controller alpha #629
Comments
/sig aws |
coming in hot under the wire here :) /milestone v1.13 |
@kacole2 Thanks! :) |
@ameukam here are the details of our progress:
What else do you need for us to show? |
/kind feature |
@d-nishi Hello - I’m the enhancement’s lead for 1.14 and I’m checking in on this issue to see what work (if any) is being planned for the 1.14 release. Enhancements freeze is Jan 29th and I want to remind that all enhancements must have a KEP - it looks like this issue has a KEP here https://github.com/kubernetes/enhancements/blob/master/keps/sig-aws/draft-20181127-aws-alb-ingress-controller.md - is that the correct KEP for this issue. |
@claurence is the ask to commit to a beta release for the feature before Jan 29th? Yes the KEP is correct. We will update it with some additional data before Jan 29th. |
@d-nishi to clarify the ask is to understand what status you are planning for this issue in the 1.14 release cycle. If that is beta I'll make sure we have that as the status being tracked. Thanks! |
@claurence yes it is beta! |
@d-nishi the KEP for this is marked as "provisional" - what open work is required for it to be "implementable"? Additionally - what open PRs in k/k should be tracked for 1.14? Code Freeze is on March 7th an all PRs need to be merged by that date. |
@claurence |
Thanks! Is there a link to the PR for that? Want to make sure all PRs are linked in the tracking sheet |
@claurence The PR to kubernetes/testinfra is merged: kubernetes/test-infra#11354 |
/milestone clear tl;dr since it sounds like this enhancements consists of bits cut from an out-of-tree repo, and the release team is only focused on kubernetes/kubernetes, we're not going to track this If there is (non-test) code in kubernetes/kubernetes that is necessary to make this plugin or out-of-tree enhancement work, please let us know |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Hi @d-nishi @M00nF1sh , I'm the 1.16 Enhancement Shadow. Is this feature going to be graduating alpha/beta/stable stages in 1.16? Please let me know so it can be added to the 1.16 Tracking Spreadsheet. Once coding begins or if it already has, please list all relevant k/k PRs in this issue so they can be tracked properly. I noticed the KEP is still in provisional state. As a reminder, every enhancement requires a KEP in an implementable state with Graduation Criteria explaining each alpha/beta/stable stages requirements. Milestone dates are Enhancement Freeze 7/30 and Code Freeze 8/29. Thank you. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In 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/test-infra repository. |
Feature Description
The text was updated successfully, but these errors were encountered: