-
Notifications
You must be signed in to change notification settings - Fork 256
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
Launching an instance using ec2-controller
service controller
#1196
Comments
Issues go stale after 90d of inactivity. |
Stale issues rot after 30d of inactivity. |
Rotten issues close after 30d of inactivity. |
@ack-bot: Closing this issue. In response to this:
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. |
Summary
Users should be able to launch and manage an EC2 Instance using
ec2-controller
service controller. The solution should be functional, align with the k8s experience, and pragmatic. For example, launching an instance should be possible with a single yaml file not requiring users to build up dependencies/infrastructure on their own.Context
This is the parent issue to track and implement work related to the ec2 instance resource controller. Feel free to comment on this issue with relevant topics or open an issue in the community repo for further discussion.
Initial Implementation for EC2 Instance resource
Instance.Status
fields depending on return types in CreateOutput shape.runInstances
api returns a list ofReservation
notInstance
instance.yaml
)update/modify
functionalities based on priorityThe text was updated successfully, but these errors were encountered: