You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 25, 2023. It is now read-only.
The module doesn't expose the instance refresh properties of the underlying auto-scaling group - so it isn't possible to trigger an instance update as part of a deployment.
I made #229 which adds the necessary properties/docs to achieve this
The text was updated successfully, but these errors were encountered:
Sorry for the delay. One issue here is whether instance refresh would work correctly and do the update without causing an outage / loss of quorum. See here for steps that you need to update the cluster. Have you actually tested it and checked there's no downtime / loss of quorum during the rollout?
The instance refresh basically automates the steps you linked to. I've
been using it for a few months now and it rotates instances solidly. On
occasions when the instances haven't launched due to my misconfiguration,
it hasn't torn down further instances and has behaved well.
One of the parameters of the refresh is the minimum healthy percentage,
which limits the number of instances it'll recycle at any one time. I have
set it so that no more than one instance at a time is taken out, but
there's nothing to stop the user setting it to a quorum-killing level! I
also set it to leave 5 minutes after a successful recycle before moving
onto the next.
I could add validation so it errors if it is set too high? Maybe I should
also add a "take care" note to the parameter since I think you can't rule
out using it to shoot yourself in the foot.
Miles
The module doesn't expose the instance refresh properties of the underlying auto-scaling group - so it isn't possible to trigger an instance update as part of a deployment.
I made #229 which adds the necessary properties/docs to achieve this
The text was updated successfully, but these errors were encountered: