https://pulumi.com logo
#kubernetes
Title
# kubernetes
w

wet-noon-14291

05/27/2020, 12:40 PM
When deploying to kubernetes I've had a couple of deploys sort of being stuck with "[1/2] Waiting for app ReplicaSet be marked available" and then failing. Is this a known issue?
a

ancient-megabyte-79588

05/27/2020, 2:28 PM
This is normally a problem in the cluster, and not a problem with Pulumi. Pulumi can experience problems when cloud resources are being provisioned and a dependent resource tries to get provisioned before the resource it depends on is ready/available. I have this problem with my
ClusterIssuer
resources.. I'm using
cert-manager
to manage certificates in my cluster, and the
lets-encrypt
ClusterIssuer.. the ClusterIssuer always fails the first tiem because cert-manager isn't ready in time. I simply have to
pulumi up
again and it works the second time. I am trying to work with the
dependsOn
parameter, but it doesn't seem to work in this case.
g

gorgeous-egg-16927

05/27/2020, 3:14 PM
As Dave said, this usually indicates a problem with the Deployment. We try to surface relevant log information, but there’s still room to improve here. It’s possible you’ll find more information about what’s going wrong with kubectl
👍 1
a

ancient-megabyte-79588

05/27/2020, 3:24 PM
kubectl, octant, the Dashboard Web UI are all good ways to explore what is happening in the cluster.
4 Views