Hi there! I activated EKS Auto mode using Pulumi EKS v3 (crosswalk). Is there a formal method to disable it? After I removed the

autoMode: {
    enabled: true,
},

the

pulumi up

failed with following errors

Diagnostics:
  pulumi:pulumi:Stack (brainfish-universe-eks-au):
    error: eks:index:Cluster resource 'brainfish-au' has a problem: grpc: the client connection is closing

  aws:eks:Cluster (brainfish-au-eksCluster):
    error:   sdk-v2/provider2.go:515: sdk.helper_schema: compute_config.enabled, kubernetes_networking_config.elastic_load_balancing.enabled, and storage_config.block_storage.enabled must all be set to either true or false: provider=aws@6.66.1
    error: diffing urn:pulumi:au::brainfish-universe-eks::eks:index:Cluster$aws:eks/cluster:Cluster::brainfish-au-eksCluster: 1 error occurred:
        * compute_config.enabled, kubernetes_networking_config.elastic_load_balancing.enabled, and storage_config.block_storage.enabled must all be set to either true or false

Additionally, I'd love to learn more about the design thinking behind the @pulumi/eks NodeGroup. It utilizes an autoscaling group in the background and requires minimum and maximum node counts. I'm curious about when it actually scales up, as I haven't noticed any changes in the machine nodes within the autoscaling group created by pulumi/eks.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

can someone explain to me the purpose of

--target

? specifically within the context

pulumi up --target

? my understanding is it allows one to target a specific resource for update, but im getting strange behavior/errors like below, which is counterintuitive to me(why is pulumi looking at/reporting on resources outside the

--target

?).

error: Resource 'urn:....' will be destroyed but was not specified in --target list.
    Either include resource in --target list or pass --target-dependents to proceed.

where the resource to be destroyed is not the targeted resource, nor should it be destroyed (it still exists in state and in the unfiltered stack) FWIW, im trying to update a provider (using

up --target

) as a workaround for this known issue where provider stored config is out of date and breaks

refresh

after a secrets rotation.

Hey, I'm using an eks/nodegroup with a custom ami and the initial provisioning works fine but if I update the

image_id

in the launch template i got the following aws error:

error: operation UPDATE failed with "InvalidRequest": You cannot specify the field releaseVersion when using custom AMIs. (Service: Eks, Status Code: 400, Request ID

i'm obviously not setting the releaseVersion, hence my confusion im using python and aws native