Add support for unmanaged nodes for AWS cloud provider

[pisymbol]

What would you like to be added:

I would like the AWS driver to support un-managed nodes like it does for Azure. See Issue #67984 for details.

Why is this needed:

The behavior is that unmanaged nodes just get automatically removed because the AWS cloud controller looks to the AWS API to determine if a node exists and to get an instance ID, but then it doesn't see it for unmanaged nodes thus it just removes it. This used to cause the scheduler to get stuck (but that was fixed in kubernetes/autoscaler#2235.

Can someone confirm that AWS has the same level of support as Azure regarding unmangaed nodes/issue #67984? We are running Kubernetes v1.13.

/platform/aws
/kind feature

[k8s-ci-robot]

@pisymbol: The label(s) sig/aws cannot be applied. These labels are supported: api-review, community/discussion, community/maintenance, community/question, cuj/build-train-deploy, cuj/multi-user, platform/aws, platform/azure, platform/gcp, platform/minikube, platform/other

In response to this:

What would you like to be added:

I would like the AWS driver to support un-managed nodes like it does for Azure. See Issue #67984 for details.

Why is this needed:

We are seeing the scheduler get stuck when there are left over un-managed AWS nodes in a given AZ. We believe it is related to Issue #67984.

Can someone confirm that AWS has the same level of support as Azure regarding unmangaed nodes/issue #67984? We are running Kubernetes v1.13.

/sig aws
/kind feature

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.

[k8s-ci-robot]

@pisymbol: The label(s) sig/platform/aws cannot be applied. These labels are supported: api-review, community/discussion, community/maintenance, community/question, cuj/build-train-deploy, cuj/multi-user, platform/aws, platform/azure, platform/gcp, platform/minikube, platform/other

In response to this:

What would you like to be added:

I would like the AWS driver to support un-managed nodes like it does for Azure. See Issue #67984 for details.

Why is this needed:

We are seeing the scheduler get stuck when there are left over un-managed AWS nodes in a given AZ. We believe it is related to Issue #67984.

Can someone confirm that AWS has the same level of support as Azure regarding unmangaed nodes/issue #67984? We are running Kubernetes v1.13.

/sig platform/aws
/kind feature

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.

[neolit123]

/sig cloud-provider

[pisymbol]

Updated issue description for clarity.

[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

[pisymbol]

IS there no interest in this at all?

[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-testing, kubernetes/test-infra and/or fejta.
/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-testing, kubernetes/test-infra and/or fejta.
/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-testing, kubernetes/test-infra and/or fejta.
/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.