@creamy-potato-29402 I’m trying to update our istio install to 1.0.7. I’m getting

**updating failed**

on most of the Deployments with a lot of errors like this:

kubernetes:extensions:Deployment (istio-system/istio-galley):
    error: Plan apply failed: 2 errors occurred:

    * Timeout occurred for 'istio-galley'
    * Minimum number of Pods to consider the application live was not attained

When i describe the pods though it looks like the images updated to 1.0.7. Have you run into this before on istio upgrades?

has anyone had an issue with helm updates to PodDisruptionBudget items? They fail with fobidden.... seems it has been a long standing issue: https://github.com/kubernetes/kubernetes/issues/45398

I am wondering if Pulumi could understand that these are immutable and handle delete/recreate?

Hi I've been using Pulumi for a few side projects recently and I'm really liking it. I just came across AWS CDK. Could someone let me know or point me in the right direction to find out the differences between the two? Thanks

I previously looked but couldn't find info on how to add tags to resources created in AWS. Any pointers?

I have a list of custom tags needed by my org to track things per department, cost center, etc

question for the team, I know the default behavior on s3 buckets is to prefix with a unique id, but I need a static bucket name for S3 is there a way to do this? I have tried setting the arn in the bucketArgs but it still created a new bucket.

I don’t know if this is reported yet, but the previews in the Web GUI use past-tense verbs like

updated

,

deleted

, and

created

which may freak out some people at first glance.

Question for everyone, are there any good examples of building unit tests/integration tests around pulumi use?

Hey 👋 Anybody knows or has examples of how to use

cognito

with

apigateway

?

Also I'm wonder if it possible to use

websocket

connection with

apigateway

right now?

is it required to have the older version of a plugin available to destroy an older stack? got this report from an engineer today:

error: could not load plugin for azure provider 'urn:pulumi:compute-g-prod-weu::compute::pulumi:providers:azure::default': no resource plugin 'azure-v0.17.2' found in the workspace or on your $PATH, install the plugin using `pulumi plugin install resource azure v0.17.2
--
running `pulumi plugin install resource azure v0.17.2` inside the container fixed it

he was using the container we built for pulumi which only had 0.17.4 installed

For

aws.ec2.KeyPair.get(...)

how would one use the

id

property for a key that already exists and wasn’t created through pulumi?

I guess maybe it’s not possible https://github.com/pulumi/pulumi/issues/1662

for the AWS provider, how do we add a RateBasedRule to a WebAcl? I've got the regular rules added fine.

is there a way of seeing what version the underlying aws provider is?

just upgraded my

@pulumi/gcp

from 0.17.4 to 0.18.3 and now pulumi is determined that it wants to replace my gke cluster with no changes. anyone got any tips for getting it to behave?

Happy Humpday. When using the awsx.ec2.Vpc to set up new VPC networks, when the internal creates the routing tables is there an easy way at the top level to add a name/tags to the built resources?

i'm using pulumi.all() against fs.promise.readFile() but the returned object is UnwrappedObject<Buffer> not an actual Buffer

how do i use that?

tostring() is returning [Object object] instead of encoding it to utf8 as it should

Hi - is there a way to create managed certificates (GKE) using pulumi?

Just filed this issue: https://github.com/pulumi/pulumi-eks/issues/100

Are there any guides/tutorials around creating your own provider?

It seems I am unable to access/reuse ts interfaces from the generated packages, e.g. pulumi-kubernetes - I want to declare and reuse an affinity but

types/input

is not accessible. e.g.

input.core.v1.Affinity

With the upstream TF bug https://github.com/pulumi/pulumi-gcp/issues/88 we are unable to migrate the cluster and do any changes to

k8s

in GKE. We are stuck, any changes we are making is causing the whole cluster to be deleted. What is the workaround?

crazy question folks: Is the SDK completely coupled to the CLI? or would i theoretically be able to execute stack operations in the context of another node.js application?

thinking of zookeeper-type scenarios

Hello, just started evaluating pulumi (I used terraform so far). Is there a components registry? similar to the terraform module registry?