Tracking issue for v2 aws provider

[andrewsykim]

What would you like to be added:
In #114 we added the initial boilerplate code to enable a v2 AWS cloud provider. This is a tracking issue for future PRs that add to the implementation.

Why is this needed:
This project will continue to support the existing AWS provider in "out-of-tree" mode. However, there are many known issues and gaps in the current provider implementation that is not trivial to address. A new v2 implementation will try to address these limitations. The v2 implementation is a breaking change from v1 and is only supported for new clusters. Existing clusters cannot upgrade to v1.

• Instances (@andrewsykim)
• Zones
• LoadBalancer (@HaibaraAi96)
• Routes

/kind feature

[andrewsykim]

/assign

Hoping to have some PRs open for this in the next week or so

[andrewsykim]

Some issues we should consider as we implement v2:
#124
#63
#55

[nicolehanjing]

I'd love to work on the loadbalancer implementation 😃

[andrewsykim]

Sounds good @HaibaraAi96! I updated the tracking issue to break up the work here a bit and assigned the loadbalancer implementation to you. Feel free to use the legacy implementation as a reference https://github.com/kubernetes/kubernetes/tree/master/staging/src/k8s.io/legacy-cloud-providers/aws

[andrewsykim]

/assign @HaibaraAi96

[rfranzke]

The v2 implementation is a breaking change from v1 and is only supported for new clusters. Existing clusters cannot upgrade to v1.

What does this mean exactly, i.e., how will existing clusters be upgraded in the future (assuming the legacy AWS cloud provider code is being removed from k/k)?

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[nckturner]

/remove-lifecycle stale

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/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.