cluster-api-provider-aws

cluster-api-provider-aws copied to clipboard

Describe the solution you'd like Default to use out-of-tree cloud provider for v1alpha2+ In tree is deprecated and we will be able to upgrade in the future.

/cc @andrewsykim /kind feature

We discussed this during the weekly meeting and agreed that it should likely be a blocker for entering Beta, but should not be a requirement for v1alpha2 since the AWS and GCP external providers are not yet feature complete compared to the in-tree providers. /milestone Next /priority important-longterm

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

/remove-lifecycle stale

/lifecycle frozen

cc @nckturner @jaypipes

/priority important-soon

/remove-lifecycle frozen

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

Bring awareness again, because this KEP plans to disable in-tree ccm in k8s 1.27

/remove-lifecycle important-longterm

/milestone v2.1.0

/remove-lifecycle rotten /help

@richardcase: This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed by commenting with the /remove-help command.

In response to this:

/remove-lifecycle rotten /help

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.

This will require changes for:

• "unmanaged" clusters - so similar to what we are doing in the e2e tests
• "managed" clusters - enabling the EKS addons

This is becoming pretty time critical:

/priority critical-urgent

@richardcase what's the scope of this issue? What needs to be done? Do we have a list of e2e that needs to be updated? or there something else?

We haven't compiled a proper list yet.