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

there is no particular reason why the first would go away.

we don’t control that, the deployment controller does.

Okay, any idea why the deployment is considered unhealthy on refresh?

it says that the resource failed to become live

what’s the status field of the deployment say?

the new RS and new pods are up, and the ReplicaSet is healthy:

```

Conditions:
  Type           Status  Reason
  ----           ------  ------
  Available      True    MinimumReplicasAvailable
```

I mean, literally the `.status` field in the deployment

```
status:
  availableReplicas: 1
  conditions:
  - lastTransitionTime: 2019-05-24T09:09:37Z
    lastUpdateTime: 2019-05-24T09:09:37Z
    message: Deployment has minimum availability.
    reason: MinimumReplicasAvailable
    status: "True"
    type: Available
  observedGeneration: 4
  readyReplicas: 1
  replicas: 1
  updatedReplicas: 1
```

is this an `extensions/v1beta1` deployment by chance?

whoa, is there a bug with v1beta1 deployments

I’m guessing you’re not on the most recent pulumi kubernetes?

I just updated Pulumi core but it's been a month or two since I updated k8s

it kind of is, the problem is that they’re not publishing that the rollout succeeded.

anyway, try upgrading and see what happens.

okay, offhand, if I update kind to `apps/v1`, what happens?

I mean, will Pulumi replace the resource correctly?

this is what review app environments are for, YOLO ¯\_(ツ)_/¯