external ccm cloudprovider-aws alpha

[d-nishi]

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]

/sig aws

[d-nishi]

/sig cloud-provider

[d-nishi]

/assign @mcrute @d-nishi

[kacole2]

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

/milestone v1.13
/stage alpha

[d-nishi]

@kacole2 - updated. Thanks for the catch.

[ameukam]

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]

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

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

[d-nishi]

/kind feature

[mcrute]

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

[mcrute]

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

[claurence]

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

@claurence yes, this is targeting 1.14 for beta

[ameukam]

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

[k8s-ci-robot]

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

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

[andrewsykim]

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

[claurence]

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

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

[claurence]

Thank you for the update!

[kacole2]

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]

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

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