brave-ambulance-9849103/17/2020, 9:24 PM
version wants me to tear down everything, which is really not ideal.
breezy-hamburger-6961903/17/2020, 11:19 PM
yep, upgrade worked correctly! nm.Ah, great. So the update worked as planned?
brave-ambulance-9849103/17/2020, 11:25 PM
breezy-hamburger-6961903/17/2020, 11:30 PM
it should probably also update the default node pool, because now i’m at a loss as to how to update that, but it does basically work as intended.The default node group is not a part of the control plane. It is a self-managed node group that pulumi creates on your behalf.  It is recommended to manage node groups separately from the control plane, that is, skipping the default node group and creating the node groups directly yourself  or having EKS manage them  for you. Note there are some trade offs  but if you manage it yourself  exists to help understand migrations, though this applies to managed nodegroups too (aws just handles the nodes but not your workloads) 1 - https://github.com/pulumi/pulumi-eks/blob/master/nodejs/eks/cluster.ts#L1069-L1077 2 - https://github.com/pulumi/pulumi-eks/tree/master/nodejs/eks/examples/nodegroup 3 - https://github.com/pulumi/pulumi-eks/tree/master/nodejs/eks/examples/managed-nodegroups 4 - https://eksctl.io/usage/eks-managed-nodegroups/#feature-parity-with-unmanaged-nodegroups 5 - https://www.pulumi.com/docs/tutorials/kubernetes/eks-migrate-nodegroups/
brave-ambulance-9849103/18/2020, 12:01 AM
breezy-hamburger-6961903/18/2020, 12:04 AM
weird that i now have an EKS cluster provisioned by pulumi whose settings will not match the settings of a cluster spun up from scratch.Could you please elaborate where the match is not occurring?
brave-ambulance-9849103/18/2020, 12:04 AM
breezy-hamburger-6961903/18/2020, 12:07 AM
brave-ambulance-9849103/18/2020, 12:10 AM
breezy-hamburger-6961903/18/2020, 12:14 AM
brave-ambulance-9849103/18/2020, 12:16 AM
breezy-hamburger-6961903/18/2020, 12:33 AM
brave-ambulance-9849103/18/2020, 12:39 AM
breezy-hamburger-6961903/20/2020, 5:13 PM