-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
update bastion machine type to variable in AWS HA terraform #47297
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So we broke the TF code by default for every x86 user 6 moths ago, but did not catch the issue until now because we default to ARM?
The new TF variable should be added to the Makefile and the README.
Also, this PR is changelog worthy. |
We don't put the other instance types (auth, proxy,...) though in the |
Thanks, changelog updated. |
The Makefile and README should contain every variable and mention if it's required or if we'll pick the default for the user. It's very likely that we missed adding variables there in the past. If you find missing vars, please add them to the reference 🙏 |
// Instance type used for bastion server | ||
variable "bastion_instance_type" { | ||
type = string | ||
default = "t4g.medium" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the interest of having a more "friendly" experience for new users, maybe we could default this to null, then conditionally set the instance type deployed based off of the AMI architecture from data.aws_ami.base
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really like this idea, but think it's probably better implemented in a future PR as it'll require a fair bit more testing.
thanks @hugoShaka, please see update. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but I'd like @webvictim 's approval before merging.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just grammar/formatting nits
// Instance type used for bastion server | ||
variable "bastion_instance_type" { | ||
type = string | ||
default = "t4g.medium" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I really like this idea, but think it's probably better implemented in a future PR as it'll require a fair bit more testing.
Co-authored-by: Gus Luxton <gus@goteleport.com>
@stevenGravy See the table below for backport results.
|
Sets to use a variable instance type instead of hard-coded. This currently causes problems if you specify a x86 AMI since that's not compatible with arm types.
changelog: Allow specifying the instance type of AWS HA Terraform bastion instance