helpful-morning-53046
07/06/2022, 4:55 PMnodeGroupOptions
as I get an error Setting nodeGroupOptions, and any set of singular node group option(s) on the cluster, is mutually exclusive. Choose a single approach.
when trying to spin up a NodeGroup (or ManagedNodeGroup) alongside the existing one.
Does anyone have any advice as to how to perform a zero downtime worker node upgrade i.e. without having to tear them all down?billowy-army-68599
helpful-morning-53046
07/07/2022, 8:25 AMeks.Cluster
input property nodeGroupOptions
to create the groups. In attempting to declare another eks.NodeGroup
manually I am receiving the error message mentioned above. I am interpreting this to mean nodeGroupOptions
are a convenient way to create single node groups but whenever you need any more complex configurations you should use eks.NodeGroup
or eks.ManagedNodeGroup
.nodeGroupOptions
but need to migrate, with zero downtime, over to the more flexible manual declarations. This was proving difficult due to the approaches being incompatible with each other. I had a realisation last night at I could just remove the nodegroups from the Pulumi state to keep them running but allow Pulumi to create new node groups alongside them.