stocky-student-9673903/29/2021, 9:29 PM
If I watch the cluster I can see all of the pods (2) in the RS stand up and become Ready, and the ReplicaSet/Deployment reports them all as up + Ready/Up-to-Date inside of 2 minutes. This is happening for every Deployment I have configured on this cluster. Tried latest
kubernetes:apps/v1:Deployment (web): error: 2 errors occurred: * the Kubernetes API server reported that "my-application/web-v845050y" failed to fully initialize or become live: 'web-v845050y' timed out waiting to be Ready * Attempted to roll forward to new ReplicaSet, but minimum number of Pods did not become live
Node module, I’m on latest Pulumi CLI binary, on EKS 1.19. I tried blowing everything up and redeploying. Nothing of note when describing the Deployment or ReplicaSet. It’s like the Pulumi client is just ignoring the state of the ReplicaSet. Any assistance would be appreciated, there’s very little out there on the Googles other than what I’ve already tried.
billowy-army-6859903/29/2021, 9:38 PM
stocky-student-9673903/29/2021, 9:38 PM
gorgeous-egg-1692703/29/2021, 10:56 PM
I0330 15:01:42.143571 1 deployment_controller.go:490] "Error syncing deployment" deployment="my-application/web-rov2l78t" err="Operation cannot be fulfilled on deployments.apps \"web-rov2l78t\": the object has been modified; please apply your changes to the latest version and try again"
gorgeous-egg-1692703/31/2021, 3:33 PM
annotation. I haven’t tested a workaround, but I expect some combination of removing that annotation and using the
annotation (https://www.pulumi.com/blog/improving-kubernetes-management-with-pulumis-await-logic/#new-annotations-to-customize-kubernetes-await-logic) would get you unblocked for now.
stocky-student-9673903/31/2021, 4:32 PM
faint-table-4272504/01/2021, 12:01 AM
stocky-student-9673904/01/2021, 12:59 AM
on the Deployment, ReplicaSet, or Pods. Adding the
notation got us past the part where we were timing out, but I don’t feel it’s a proper solution since it’s just firing and forgetting and not concerned with the ultimate state of the deployment.
able-afternoon-7308005/12/2021, 2:08 PM
stocky-student-9673907/01/2021, 3:44 PM
sparse-park-6896707/07/2021, 10:59 PM
) would be very useful. Happy to setup time with you if you are concerned about sharing the detailed logs.
pulumi --logflow --verbose=9 --debug --logtostderr up --yes >& /tmp/logs
stocky-student-9673907/07/2021, 11:01 PM
sparse-park-6896707/08/2021, 8:20 PM
stocky-student-9673907/08/2021, 8:25 PM
sparse-park-6896707/08/2021, 8:44 PM