👋 Hi everyone!

+   └─ awsx:ecr:Image                             image               created (0.39s)

+ └─ dockerindexImage 2ede5c99-container creating failed 1 error Diagnostics: dockerindexImage (2ede5c99-container): error: error reading build output: failed to read downloaded context: failed to load cache key: invalid response status 403 When trying to use example from doc:

package myproject;

import com.pulumi.Context; import com.pulumi.Pulumi; import com.pulumi.awsx.ecr.Repository; import com.pulumi.awsx.ecr.RepositoryArgs; import com.pulumi.awsx.ecr.Image; import com.pulumi.awsx.ecr.ImageArgs; public class App { public static void main(String[] args) { Pulumi.run(App::stack); } public static void stack(Context ctx) { var repository = new Repository("repository", RepositoryArgs.builder() .forceDelete(true) .build()); var image = new Image("image", ImageArgs.builder() .repositoryUrl(repository.url()) .context("./app") .platform("linux/amd64") .build()); ctx.export("url", repository.url()); } }

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.

This message was deleted.

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.