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

```
kubectl get nodes
NAME                                         STATUS   ROLES    AGE    VERSION
ip-10-213-18-34.us-west-2.compute.internal   Ready    &lt;none&gt;   123m   v1.12.7
ip-10-213-5-19.us-west-2.compute.internal    Ready    &lt;none&gt;   124m   v1.12.7
```

This may have to do with deploying into the kube-system namespace?

This _seems_ to be a problem specific to Pulumi. I can't find any k8s resources on this issue.

I don't think Pulumi is respecting the `namespace` property set on the `k8s.helm.v2.Chart`.

FWIW I have tried to use the `namespace` property and it had no effect on which namespace the pods were deployed to

Perhaps this? <https://github.com/pulumi/pulumi-kubernetes/issues/576>

Wow, most of the issues in the kubernetes repo have to do with namespaces haha.

pulumi is looking at the resources and trying to determine if they’re alive.

it does not look like they’re alive so we error out.

the application step is identical to `kubectl apply` so there is a really high chance that this app is not healthy.

I created a small repro here: <https://github.com/pulumi/pulumi-kubernetes/issues/578>

I deleted that stack. I can try creating it again.

if the pods are not alive, then it’s not a pulumi bug

I forget exactly what happened. I'll create the stack again.