If I'm using pulumi-eks, and creating a separate m...
# kubernetes
f
If I'm using pulumi-eks, and creating a separate managedNodeGroup - what's the right way to go about triggering a refresh of the instance group nodes when the EKS version is updated? I believe the nodes pull their k8s version from the control plane on startup.
Turns out, the managednodegroup has its own field for version. Updating that along with the cluster version took care of it