Hello. I was wondering if someone has encounter this issue? I followed the step to ignore or force apply but the issue still persists

pulumi:pulumi:Stack (dev-aks-dev):
    error: preview failed

  kubernetes:admissionregistration.k8s.io/v1:MutatingWebhookConfiguration (akv2k8s:akv2k8s/akv2k8s-envinjector):
    error: Preview failed: 1 error occurred:
        * the Kubernetes API server reported that "akv2k8s-envinjector" failed to fully initialize or become live: Server-Side Apply field conflict detected. See <https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/#handle-field-conflicts-on-existing-resources> for troubleshooting help.
    The resource managed by field manager "pulumi-kubernetes-76f53175" had an apply conflict: Apply failed with 1 conflict: conflict with "admissionsenforcer" using admissionregistration.k8s.io/v1: .webhooks[name="pods.env-injector.admission.spv.no"].namespaceSelector

Pulumi attempts to apply changes to the Kubernetes resource MutatingWebhookConfiguration named akv2k8s-envinjector. Specifically, the conflict is with a field managed by another field manager called admissionsenforcer

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.

Hey folks. I'm using pulumi to deploy helm charts into my GKE cluster but for whatever reason, the admin kubeconfig isn't consistently used. I'll need to sign in with my own gcloud get-credentials, type my password, etc. before pulumi will work. This also means running pulumi in github actions is just downright broken. I'm using the gcp-py-gke example exactly but the workflow seems broken. Hopefully I'm just doing something a little bit wrong. Any advices? (cc @Tyler Hayden)

Any chance to skip resources (programatically) during refresh/preview/update if for example I don’t have an API key access as a pulumi runner. User story: The CI has access to a secret I do not have. This secret is used for some complementary resources in my stack. However other parts of the Pulumi stack (the main resources) - I do have access to, from my own machine I would like: • If I run pulumi up from CI - everything works • If I run pulumi up from my machine - I detect that I do not have access to the API key, and I skip the creation/deletion of such resources ◦ If resources exist in the stack - they are still in the stack after the operation, just unchanged ◦ If I try to delete the stack, I only succeed to delete the resources that I can delete. Skipped resources and dependent resources will not be deleted, destroying the stack will fail - since I can not access those resources. Obviously I can create those resources in a different sibling/sub-stack, but I was wondering if this is possible to do in a single stack

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.