This message was deleted.
# general
s
This message was deleted.
c
there is no particular reason why the first would go away.
the GC might pick it up, but it depends.
o
Okay
c
we don’t control that, the deployment controller does.
o
Ah, right
Okay, any idea why the deployment is considered unhealthy on refresh?
c
it says that the resource failed to become live
what’s the status field of the deployment say?
o
the new RS and new pods are up, and the ReplicaSet is healthy:
Copy code
Conditions:
  Type           Status  Reason
  ----           ------  ------
  Available      True    MinimumReplicasAvailable
c
I mean, literally the
.status
field in the deployment
o
Copy code
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
c
is this an
extensions/v1beta1
deployment by chance?
o
it is
whoa, is there a bug with v1beta1 deployments
c
I’m guessing you’re not on the most recent pulumi kubernetes?
o
hm
may not be
I just updated Pulumi core but it's been a month or two since I updated k8s
c
it kind of is, the problem is that they’re not publishing that the rollout succeeded.
o
okay
c
we fixed this a few weeks ago
maybe months ago
anyway, try upgrading and see what happens.
o
okay, offhand, if I update kind to
apps/v1
, what happens?
c
same issue.
oh
you mean in the definition?
o
I mean, will Pulumi replace the resource correctly?
yeah
c
it should work.
is my guess
o
this is what review app environments are for, YOLO ¯\_(ツ)_/¯