@@ -700,6 +700,39 @@ policy permissions. `Information on how to correctly set these permissions can
700700be found here
701701<https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/enable-access-logs.html#attach-bucket-policy> `_.
702702
703+ Spot Instances
704+ ~~~~~~~~~~~~~~
705+ Tarmak gives the ability to attempt to request spot instances for use in
706+ instance pools. Spot instances are very cheap, spare AWS instances that can be
707+ revoked by AWS at any time, given a 2 minute notification. `More information
708+ here <https://aws.amazon.com/ec2/spot/> `_.
709+
710+ Spot instances can be requested cluster-wide by giving the ``--spot-pricing ``
711+ flag to ``cluster apply ``. Tarmak will then attempt a best effort spot price for
712+ each instance pool in the cluster, calculated as the average spot price in the
713+ last 3 days for that instance type in each zone plus 25%.
714+
715+ Manual spot prices can be applied to each instance pool within the
716+ ``tarmak.yaml `` which will override the Tarmak best effort for that instance
717+ pool. This is done through the ``spotPrice `` attribute under the instance pool,
718+ given as a number in USD. This can be added like so:
719+
720+ .. code-block :: yaml
721+
722+ - image : centos-puppet-agent
723+ maxCount : 3
724+ metadata :
725+ creationTimestamp : " 2018-07-27T09:33:15Z"
726+ name : worker
727+ minCount : 3
728+ size : medium
729+ spotPrice : 0.015
730+
731+
732+ Note that Tarmak will only attempt to create spot instances for instance pools
733+ with the ``spotPrice `` attribute or spot pricing flag during a cluster apply.
734+
735+
703736Cluster Services
704737----------------
705738
@@ -721,3 +754,4 @@ Do the following steps to access Grafana:
721754.. code-block :: none
722755
723756 http://127.0.0.1:8001/api/v1/namespaces/kube-system/services/monitoring-grafana/proxy/
757+
0 commit comments