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

This is from a kubernetes deployment?  Sounds like a network error while watching the kubernetes master. Cc <@UBAJ7TD53> 

Yes sorry, this was logged under a `pulumi:pulumi:Stack` output and the only error I got else than that was a kubernetes deployment which failed with a timeout

<@UB3BGTV63> <@UEG5UEQ4U> this tends to happen when the API server becomes unavailable to your machine in the middle of an update. I see it sometimes when I have a reaaaaallly slow Internet connection, as I do on the reservation.

I think the error message could improve, but there’s also a bunch of errors like this that are deep in client-go, which I’m not sure how to get at.

<@UBAJ7TD53> thanks for the follow up.
If I remember well, I got this problem because of a missing `dependsOn` in my deployment flow which seems to have lead to an unexpected error and timeout. Once I added explicitly the dependency the problem was gone.

could be — I’m not 100% sure why the error happens, only that I see it occasionally when I have a very unreliable internet connection.

It does _look_ more alarming than it is. YOu aren’t being rate limited, I don’t think — this seems to be a protocol-level thing.

Yes I’m pretty sure the problem was not related to my connection at that time. (It could be my VPN though, but usually when I have an issue like that I test twice with and without the VPN to be sure it’s not related)

if you ever get around to reliably reproducing it please file a bug.

I’ve tried to track it down, but it’s too uncommon for me to make real progress