https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
w
being stuck on updating
Do you have more details on this?
c
Getting them for you now
Copy code
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.
When viewing details, no differences are shown
w
Same question as parallel thread - are you on latest Pulumi-kubernetes? I know there are some fixes related to Deployment await logic recently.
c
Yes I am
Even then, it shouldn’t be detecting any changes
Because there are none
And that is the actual issue
g
Hey @cool-egg-852, 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.
c
What exactly is it you are looking for?
g
Are you deploying a helm chart? I’m looking for a repro, if possible
c
No, this is not a helm chart.
This is a custom deployment
I DMed you the diff output
👍 1
9 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

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.

Powered by