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

[QT-525] enos: use spot instances for Vault targets #20037

Merged
merged 2 commits into from
Apr 13, 2023
Merged

[QT-525] enos: use spot instances for Vault targets #20037

merged 2 commits into from
Apr 13, 2023

Commits on Apr 7, 2023

  1. [QT-525] enos: use spot instances for Vault targets 

    The previous strategy for provisioning infrastructure targets was to use
the cheapest instances that could reliably perform as Vault cluster
nodes. With this change we introduce a new model of bidding for spot
fleet instances with the goal of costs savings and often more powerful
instances. The spot fleet instance bidding has only been implemented for
Vault clusters. Updating our Consul backend bidding will be handled in
another PR.

* Create a new `vault_cluster` module that handles installation,
  configuration, initializing, and unsealing Vault clusters.
* Create a `target_ec2_instances` module that can provision a group of
  instances on-demand.
* Create a `target_ec2_spot_fleet` module that can bid on a fleet of
  spot instances.
* Extend every Enos scenario to utilize the spot fleet target acquisition
  strategy and the `vault_cluster` module.
* Update our Enos CI modules to handle both the `aws-nuke` permissions
  and also the privileges to provision spot fleets.

Signed-off-by: Ryan Cragun <me@ryan.ec>
    @ryancragun
    ryancragun committed Apr 7, 2023
    Configuration menu
    Copy the full SHA
    23f5b16 View commit details
    Browse the repository at this point in the history

  2. use us-east-1 instead of us-west-1 because it's cheaper 

    Signed-off-by: Ryan Cragun <me@ryan.ec>
    @ryancragun
    ryancragun committed Apr 7, 2023
    Configuration menu
    Copy the full SHA
    e3862c5 View commit details
    Browse the repository at this point in the history