Getting an interesting error.. not sure what is causing this nor can I find anything in the pulumi repo what could cause this error `13 INTERNAL: Request message serialization failure: b.Va is not a function`:

Diagnostics:
  pulumi:pulumi:Stack (k8s-production):
    warning: using pulumi-resource-pnap from $PATH at [PATH]/k8s-pulumi/pulumi-pnap/bin/pulumi-resource-pnap
    error: Running program '[PATH]/k8s-pulumi/pulumi-k8s/k8s/' failed with an unhandled exception:
    <ref *1> Error: failed to register new resource k8s-prd-3-configurationApply [talos:machine/configurationApply:ConfigurationApply]: 13 INTERNAL: Request message serialization failure: b.Va is not a function
        at Object.registerResource ([PATH]/k8s-pulumi/pulumi-k8s/node_modules/@pulumi/runtime/resource.ts:455:27)
        at new Resource ([PATH]/k8s-pulumi/pulumi-k8s/node_modules/@pulumi/resource.ts:507:13)
        at new CustomResource ([PATH]/k8s-pulumi/pulumi-k8s/node_modules/@pulumi/resource.ts:962:9)
        at new ConfigurationApply ([PATH]/k8s-pulumi/pulumi-k8s/node_modules/@pulumiverse/machine/configurationApply.ts:114:9)
        at createTalosCluster ([PATH]/k8s-pulumi/pulumi-k8s/common/talos.ts:66:43)
        at Object.<anonymous> ([PATH]/k8s-pulumi/pulumi-k8s/k8s/index.ts:10:53)
        at Module._compile (node:internal/modules/cjs/loader:1256:14)
        at Module.m._compile ([PATH]/k8s-pulumi/pulumi-k8s/node_modules/ts-node/src/index.ts:439:23)
        at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
        at Object.require.extensions.<computed> [as .ts] ([PATH]/k8s-pulumi/pulumi-k8s/node_modules/ts-node/src/index.ts:442:12) {
      promise: Promise { <rejected> [Circular *1] }
    }

This message was deleted.

This message was deleted.

Hello, I have a Pulumi project for managing my AWS Organization and SSO (IAM Identity Center). Everything was working perfectly two months ago. Before implementing new changes, I decided to run a

pulumi up

to ensure everything was still in order. However, during the preview, Pulumi is attempting to delete and recreate the Organization, and of course replace all my OUs and update all my Accounts. This behavior seems unusual, and I’m unable to understand why it’s happening. It's unclear why Pulumi wants to delete and recreate my organization. Could you help me troubleshoot this issue? Thank you in advance for your assistance!

Hi! I am trying to setup Pulumi with Azure backend (Blob Storage) using az login from this documentation: https://www.pulumi.com/docs/concepts/state/#azure-blob-storage It is mentioned that "The Azure account must have the Storage Blob Data Contributor role or an equivalent role with permissions to read, write, and delete blobs." I have a contributor role on my account, and can manage blob storage and its containers, but I am getting: "RESPONSE 403: 403 This request is not authorized to perform this operation using this permission." Two questions: • Is Pulumi looking EXACTLY for this role to be assigned to the logged-in account? • Is it possible to setup this in a way, that only the READER role is required, so I could use Preview but not Up? (local machine development)

This message was deleted.

Is there a way to use podman with pulumi? Use case: 1. Have a podman (OCI) image get built (can be done outside of pulumi script if needed) 2. Push it to ECR 3. Use it as a lambda image

This message was deleted.

Hey, Using EKS and metrics-server(from the helm chart) I have this error, I created the cluster using the pulumi guide with EKS and node groups. I have the aws-node, with the CNI installed (but not the addon)

E0729 17:05:11.585565       1 scraper.go:149] "Failed to scrape node" err="Get \"<https://10.0.12.191:10250/metrics/resource>\": remote error: tls: internal error" node="ip-10-0-12-191.us-west-2.compute.internal"
E0729 17:05:46.982621       1 scraper.go:147] "Failed to scrape node, timeout to access kubelet" err="Get \"<https://10.0.158.73:10250/metrics/resource>\": context deadline exceeded" node="ip-10-0-158-73.us-west-2.compute.internal" timeout="10s"

I have other deployment working fine, Also I can use HPA with CPU based autoscaling. But I have random warning in the cluster by the HPA (failed to get cpu utilization: unable to get metrics for resource cpu: unable to fetch metrics from resource metrics API: the server could not find the requested resource (get pods.metrics.k8s.io)\

This message was deleted.