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.

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

Add support for unmanaged nodes for AWS cloud provider #83636

Open
pisymbol opened this issue Oct 8, 2019 · 4 comments

Comments

@pisymbol
Copy link

commented Oct 8, 2019

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

This comment has been minimized.

Copy link
Contributor

commented Oct 8, 2019

@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

This comment has been minimized.

Copy link
Contributor

commented Oct 8, 2019

@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

This comment has been minimized.

Copy link
Member

commented Oct 9, 2019

/sig cloud-provider

@pisymbol

This comment has been minimized.

Copy link
Author

commented Oct 10, 2019

Updated issue description for clarity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.