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

I dug into the pulumi source to grab the serialized YAML being sent to the grpc function, but remarkably, it lints.

I can't get any info on what is actually producing this error

Yup, previously working untouched stack produces the same error on pulumi up -y.  Something broken on pulumi's end (or whatever this grpc call is hitting)

Appears to be that permissions had become 555 or something on my ~/.kube/config, resulting in what appeared to be a YAML error when kubernetes:yaml:decode was called.  Nasty bug

Would you mind filing an issue with more details? Sorry for the obtuse error message there. Trying to make the reasons clearer when stuff goes wrong