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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

[EKS] [request]: Reset Managed Node Group status #2326

Open
nsilve opened this issue Apr 8, 2024 · 0 comments
Open

[EKS] [request]: Reset Managed Node Group status #2326

nsilve opened this issue Apr 8, 2024 · 0 comments
Labels
EKS Managed Nodes EKS Managed Nodes EKS Amazon Elastic Kubernetes Service Proposed Community submitted issue

Comments

@nsilve
Copy link

nsilve commented Apr 8, 2024

Community Note

  • Please vote on this issue by adding a 馃憤 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Tell us about your request
We would like to have an alternative way to make an EKS Managed Node Group active/healthy again after a scale out failure.

Which service(s) is this request for?
EKS

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Right now, when an EKS Managed Node Group does not succeed to scale out (due to capacity unavailability), its status becomes degraded. The only way to reset its status back to active/healthy is to successfully scale out. Even if we scale this EKS Managed Node Group to zero, its status remains degraded. So in case that AWS runs out of capacity for the specific instance type/az of this EKS Managed Node Group, it would remain in degraded status forever.
We would like to have an alternative way to reset its status back to active/healthy status.
The problem is that we need to make some exceptions to our tools/monitoring e.g. for EKS Managed Node Group scaled to zero but in degraded status.

Are you currently working around this issue?
We implement some very custom exceptions to our tools/monitoring.

@nsilve nsilve added the Proposed Community submitted issue label Apr 8, 2024
@mikestef9 mikestef9 added EKS Amazon Elastic Kubernetes Service EKS Managed Nodes EKS Managed Nodes labels Apr 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
EKS Managed Nodes EKS Managed Nodes EKS Amazon Elastic Kubernetes Service Proposed Community submitted issue
Projects
None yet
Development

No branches or pull requests

2 participants