cluster-api-provider-aws
cluster-api-provider-aws copied to clipboard
Support EC2 Serial Console
/kind feature /help
Describe the solution you'd like I would like the option of enabling the EC2 Serial Console for the EC2 instances that are created via CAPA (both unmnagaed and managed).
Anything else you would like to add:
Environment:
- Cluster-api-provider-aws version: 0.6.4
@richardcase: This request has been marked as needing help from a contributor.
Please ensure the request meets the requirements listed here.
If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.
In response to this:
/kind feature /help
Describe the solution you'd like I would like the option of enabling the EC2 Serial Console for the EC2 instances that are created via CAPA (both unmnagaed and managed).
Anything else you would like to add:
Environment:
- Cluster-api-provider-aws version: 0.6.4
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.
/milestone v0.7.x
Not sure how important it is given you'll need to set username and passwords to do anything useful with it.
I agree its a low priority.
/priority backlog
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale
/lifecycle frozen
/remove-lifecycle frozen
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale