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

So, I had a `replicas` property on my Deployment `spec` *and* the `template.spec`. It's odd that `pulumi up` has worked until I changed the `livenessProbe` property on a different Deployment.

I mean, it’s telling you that your deployment does not actually satisfy the schema.

`replicas` does not go in the pod spec, right?

Pulumi is just faithfully reporting the error.

It’s just weird that the deployment was working with no errors until the livenessProbe change. 

i don’t know about that, but the error here seems to tell you what to fix?

Yes. The concerning part was that I did not receive that message until other, unrelated changes occurred.

was something in the liveness probe a computed value?

Given it's a TSError, I would've thought it would always fail.

I have no idea, but the TS compiler does a lot of guessing.

It’s more like a heuristic engine than a safe type checker.

I also know that I had several successful deploys with `initialDelaySeconds` set in `readinessProbe.httpGet` instead of just `readinessProbe`.