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.

Sign up for GitHub

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

Jump to bottom

Handle stopped/ terminated ec2 instances #866

Closed
ashish-amarnath opened this issue Jul 1, 2019 · 2 comments
Closed

Handle stopped/ terminated ec2 instances #866

ashish-amarnath opened this issue Jul 1, 2019 · 2 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
v0.4.0 (v1alpha2)

Comments

@ashish-amarnath
Copy link
Contributor

/kind feature

Describe the solution you'd like
When an EC2 instance backing a k8s node is stopped or terminated (generalized on 'goes away'), capa actuator should update the actual state of the machine object to "vm-lost" (or something) so the machine goes into an error state.

Anything else you would like to add:

Environment:

  • Cluster-api-provider-aws version:
  • Kubernetes version: (use kubectl version):
  • OS (e.g. from /etc/os-release):
@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Jul 1, 2019
@ncdc ncdc added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Jul 15, 2019
@ncdc ncdc added this to the v0.4 milestone Jul 15, 2019
@ncdc
Copy link
Contributor

ncdc commented Aug 1, 2019

This is implemented in master. Also xref kubernetes-sigs/cluster-api#1205
/close

@k8s-ci-robot
Copy link
Contributor

@ncdc: Closing this issue.

In response to this:

This is implemented in master. Also xref kubernetes-sigs/cluster-api#1205
/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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
v0.4.0 (v1alpha2)
Development

No branches or pull requests
3 participants
@ncdc @k8s-ci-robot @ashish-amarnath