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

AWS: Support for passing CpuOptions #1726

Open
glachac-safelishare opened this issue Oct 25, 2023 · 6 comments
Open

AWS: Support for passing CpuOptions #1726

glachac-safelishare opened this issue Oct 25, 2023 · 6 comments
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management.

Comments

@glachac-safelishare
Copy link

Add support for setting the EC2 instance CpuOptions in the AWS provider.

We can set ami, instanceType, etc, but some workloads need cpu features turned on in the instance that are only enabled by setting values in CpuOptions; specifically, AmdSevSnp.
@embik embik added the sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management. label Oct 30, 2023
@embik
Copy link
Member

embik commented Oct 30, 2023

Thank you for opening this issue @glachac-safelishare. We are always open to contributions, but have also added this to our backlog for future consideration.

Is there a list of all available cpu options available somewhere? I found the feature mentioned here and here, but I found the second link only because the issue mentions AmdSevSnp. It's not linked on the first page, which seems like the "generic" page describing the feature.

@glachac-safelishare
Copy link
Author

I mostly use terraform, and they expose three options documented here: https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/instance#cpu-options, with links to the underlying AWS docs

@embik embik added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Nov 7, 2023
@kubermatic-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@kubermatic-bot kubermatic-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 5, 2024
@embik
Copy link
Member

embik commented Feb 5, 2024

/remove-lifecycle stale

@kubermatic-bot kubermatic-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 5, 2024
@kubermatic-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@kubermatic-bot kubermatic-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 5, 2024
@embik
Copy link
Member

embik commented May 6, 2024

/remove-lifecycle stale

@kubermatic-bot kubermatic-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. sig/cluster-management Denotes a PR or issue as being assigned to SIG Cluster Management.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@embik @kubermatic-bot @glachac-safelishare