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

After restarting the machine that was running the single-system method EKS Anywhere, I lost my EKS-A Cluster. #187

Closed
ruiyaoOps opened this issue Sep 13, 2021 · 4 comments
Labels
priority/p1 On the list but not scheduled status/notstarted

Comments

@ruiyaoOps
Copy link

What happened:
After restarting the machine that was running the single-system method EKS Anywhere, I lost my EKS-A Cluster.

What you expected to happen:
After restarting the machine, the single-system method EKS Anywhere will restart too.

How to reproduce it (as minimally and precisely as possible):
Restarting the machine that was running the single-system method EKS Anywhere.

Anything else we need to know?:

Environment:

  • EKS Anywhere Release: v0.5.0
  • EKS Distro Release:

image
image

@jaxesn
Copy link
Member

jaxesn commented Sep 13, 2021

Thanks for the report. I have added +1 to track future instances from other users.

@jaxesn
Copy link
Member

jaxesn commented Sep 13, 2021

This is fixed upstream in capi v0.4

kubernetes-sigs/cluster-api#5021

@jaxesn jaxesn added status/notstarted priority/p1 On the list but not scheduled labels Sep 13, 2021
@jaxesn jaxesn added this to the next+1 milestone Sep 13, 2021
@ganga-sah
Copy link

I am eagerly waiting for a fix for this issue. Currently EKSA on docker running on MacOS or Windows is not useful as I don't know of a way to restart EKSA cluster on docker or machine restart. Is there any workaround to restart EKSA cluster?

@jaxesn jaxesn modified the milestones: next+1, next Nov 8, 2021
@jaxesn
Copy link
Member

jaxesn commented Jan 12, 2022

The fix for this will be included in our release later this month.

@jaxesn jaxesn closed this as completed Jan 12, 2022
@jaxesn jaxesn removed this from the next milestone Feb 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/p1 On the list but not scheduled status/notstarted
Projects
None yet
Development

No branches or pull requests

3 participants