cluster-api-provider-aws
cluster-api-provider-aws copied to clipboard
Support for ephemeral instance storage volumes in AWSMachineTemplate
/kind feature
Describe the solution you'd like I would like the ability to provision nodes with ephemeral instance store volumes attached. https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/add-instance-store-volumes.html
This would allow another option for high performance disk to be available for scratch storage in our clusters.
Anything else you would like to add: Slack thread for more context: https://kubernetes.slack.com/archives/CD6U2V71N/p1614199967028000 Naadir Jeewa suspects that this can be implemented via BlockDeviceMappings, and that we only need to distinguish between EBS and ephemeral storage.
Terraform docs on the spec for instance store volumes, in case it is helpful. https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/instance#ephemeral_block_device
Environment:
- Cluster-api-provider-aws version: 0.6.4
/help
@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:
/help
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.
@richardcase would this be useful? https://github.com/brunsgaard/eks-nvme-ssd-provisioner
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
/priority backlog /triage accepted /help
/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
This issue has not been updated in over 1 year, and should be re-triaged.
You can:
- Confirm that this issue is still relevant with
/triage accepted(org members only) - Close this issue with
/close
For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/
/remove-triage accepted