Skip to content
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.

Sign up for GitHub

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

Jump to bottom

external ccm cloudprovider-aws alpha #631

Closed
d-nishi opened this issue Oct 24, 2018 · 23 comments
Closed

external ccm cloudprovider-aws alpha #631

d-nishi opened this issue Oct 24, 2018 · 23 comments
Assignees
@mcrute @d-nishi
Labels
area/provider/aws Issues or PRs related to aws provider kind/feature Categorizes issue or PR as related to a new feature. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team

Comments

@d-nishi
Copy link
Contributor

d-nishi commented Oct 24, 2018 •
edited
Loading

Feature Description

  • One-line feature description (can be used as a release note): The external cloud controller manager aws would be responsible for running controllers whose function is specific to aws cloud provider functionality.
  • Primary contact (assignee): @mcrute
  • Responsible SIGs: SIG AWS
  • Design proposal link (community repo): KEP - https://github.com/kubernetes/community/blob/master/keps/sig-cloud-provider/0002-cloud-controller-manager.md
  • Link to e2e and/or unit tests: will update later.
  • Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @justinsb @andrewsykim
  • Approver (likely from SIG/area to which feature belongs): @d-nishi
  • Feature target (which target equals to which milestone):
    • Alpha release target (1.13)
    • Beta release target (1.14)
    • Stable release target (1.15)
@d-nishi
Copy link
Contributor Author

d-nishi commented Oct 24, 2018

/sig aws

@k8s-ci-robot k8s-ci-robot added the area/provider/aws Issues or PRs related to aws provider label Oct 24, 2018
@d-nishi
Copy link
Contributor Author

d-nishi commented Oct 24, 2018 •
edited
Loading

/sig cloud-provider

@k8s-ci-robot k8s-ci-robot added the sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. label Oct 24, 2018
@d-nishi
Copy link
Contributor Author

d-nishi commented Oct 24, 2018

/assign @mcrute @d-nishi

@kacole2
Copy link

kacole2 commented Oct 24, 2018

@d-nishi your copy/pasta from #630 has the same descriptor

/milestone v1.13
/stage alpha

@kacole2 kacole2 added this to the v1.13 milestone Oct 24, 2018
@kacole2 kacole2 added stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Oct 24, 2018
@d-nishi
Copy link
Contributor Author

d-nishi commented Oct 24, 2018

@kacole2 - updated. Thanks for the catch.

@ameukam
Copy link
Member

ameukam commented Nov 6, 2018

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!

@mcrute
Copy link
Contributor

mcrute commented Nov 7, 2018 •
edited
Loading

@ameukam the current state of this is:

  1. Code is complete and being tested
  2. CI signal is WIP
  3. Docs are WIP

Do we need to show anything else?

WIP cloud-provider-aws

@ameukam
Copy link
Member

ameukam commented Nov 8, 2018

@mcrute Thank you for the update! Please can you add the links for the CI Signal and the Docs ?

@d-nishi
Copy link
Contributor Author

d-nishi commented Nov 9, 2018

/kind feature

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Nov 9, 2018
@mcrute
Copy link
Contributor

mcrute commented Nov 15, 2018

The CI signal is pending kubernetes/test-infra#10151

@mcrute
Copy link
Contributor

mcrute commented Nov 16, 2018 •
edited
Loading

The docs are pending kubernetes/cloud-provider-aws#21 which is WIP

@andrewsykim andrewsykim mentioned this issue Dec 4, 2018
Closed
@claurence
Copy link

@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.

@mcrute
Copy link
Contributor

mcrute commented Jan 15, 2019

@claurence yes, this is targeting 1.14 for beta

@ameukam
Copy link
Member

ameukam commented Jan 22, 2019

/remove-milestone v1.13
/milestone v1.14

@k8s-ci-robot
Copy link
Contributor

@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.

@claurence claurence modified the milestones: v1.13, v1.14 Jan 22, 2019
@claurence
Copy link

@mcrute thanks! Any open PRs we should track for 1.14?

@andrewsykim andrewsykim mentioned this issue Jan 28, 2019
Merged
@andrewsykim
Copy link
Member

FYI put together the boiler plate for this KEP here #735

@claurence
Copy link

@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.

@mcrute
Copy link
Contributor

mcrute commented Feb 11, 2019

@claurence we're going to push this out to 1.15 I'll work on updating the KEP for that release

@claurence
Copy link

Thank you for the update!

@claurence claurence added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Feb 11, 2019
@claurence claurence removed this from the v1.14 milestone Feb 11, 2019
@kacole2
Copy link

kacole2 commented Apr 12, 2019

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.

@mcrute
Copy link
Contributor

mcrute commented Apr 17, 2019

@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

@k8s-ci-robot
Copy link
Contributor

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mcrute mcrute

@d-nishi d-nishi

Labels
area/provider/aws Issues or PRs related to aws provider kind/feature Categorizes issue or PR as related to a new feature. sig/cloud-provider Categorizes an issue or PR as relevant to SIG Cloud Provider. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@mcrute @ameukam @kacole2 @andrewsykim @claurence @d-nishi @k8s-ci-robot