No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

We’re having an issue with a k8s deployment being stuck on updating though it isn’t actually updating anything. This is critically breaking us from being able to deploy updated applications because it’s breaking CI with it being stuck.

&gt; being stuck on updating

Do you have more details on this?

```

error: Plan apply failed: 2 errors occurred:
	* Timeout occurred for 'istio-ingressgateway-internal'
	* Minimum number of Pods to consider the application live was not attained
```

It doesn’t have any changes for it though. I copied this from the pulumi console, but I am noticing that the pulumi console doesn’t have the same output as CLI, so it isn’t showing that it has to update on the console, but it is in the CLI

I’m running up now to get the CLI output

I would consider the console not showing the same information to be a bug in the console.

image.png

When viewing details, no differences are shown

Same question as parallel thread - are you on latest Pulumi-kubernetes?  I know there are some fixes related to Deployment await logic recently. 

Even then, it shouldn’t be detecting any changes

Hey <@UGDSK5RNC>, can you provide any more information on the stack you’re updating?

AFAICT, the problem seems to be with the diff logic, but I don’t have enough info to reproduce on my end.

Are you deploying a helm chart? I’m looking for a repro, if possible