bored-table-20691
06/03/2021, 5:20 AMSpec: &corev1.PodSpecArgs{
ServiceAccountName: tenant.serviceAccount.Metadata.Name(),
Let’s say I had the above, and then I just deleted the ServiceAccountName line. Pulumi seems to recognize that it should do an update, but nothing happens on the Kubernetes side (the Deployment is not updated, the pod does not restart), and Pulumi hangs waiting for something to happen ([diff: ~spec]; [1/2] Waiting for app ReplicaSet be marked available (1/1 Pods available)
).
Any ideas what might be going on?billowy-army-68599
06/03/2021, 5:42 AMbored-table-20691
06/03/2021, 5:47 AMbillowy-army-68599
06/03/2021, 5:49 AMbored-table-20691
06/03/2021, 5:53 AMbillowy-army-68599
06/03/2021, 5:54 AMpulumi up
?bored-table-20691
06/03/2021, 5:54 AMpulumi preview
but I can change it to pulumi up
billowy-army-68599
06/03/2021, 5:54 AMdetails
option, that'll give you the full diffbored-table-20691
06/03/2021, 5:55 AMDo you want to perform this update? details
pulumi:pulumi:Stack: (same)
[urn=urn:pulumi:tenant-itay7::okera-trial-tenants::pulumi:pulumi:Stack::okera-trial-tenants-tenant-itay7]
> pulumi:pulumi:StackReference: (read)
[id=itay/okera-infra-regions/us-west-2]
[urn=urn:pulumi:tenant-itay7::okera-trial-tenants::pulumi:pulumi:StackReference::itay/okera-infra-regions/us-west-2]
name: "itay/okera-infra-regions/us-west-2"
~ kubernetes:apps/v1:Deployment: (update)
[id=itay7/cdas-rest-server]
[urn=urn:pulumi:tenant-itay7::okera-trial-tenants::kubernetes:apps/v1:Deployment::cdas_rest_serverDeployment]
~ spec: {
~ template: {
~ spec: {
- serviceAccountName: <null>
}
}
}
billowy-army-68599
06/03/2021, 5:56 AMbored-table-20691
06/03/2021, 5:57 AMbillowy-army-68599
06/03/2021, 5:57 AMbored-table-20691
06/03/2021, 5:57 AMbillowy-army-68599
06/03/2021, 5:58 AMkubectl describe pod <name>
and it'll tell you thisbored-table-20691
06/03/2021, 5:58 AMpulumi up
with the above, it still has the servie accountbillowy-army-68599
06/03/2021, 6:00 AMkubectl describe pod
and kubectl get pod -o yaml
? feel free to DM it to me in a github giststeep-toddler-94095
06/03/2021, 6:00 AMbillowy-army-68599
06/03/2021, 6:01 AMI did pulumi up, and Kubernetes is showing no update of the pod/Deploymentit seems that's not true, the pod/replicaset is updating but it's not becoming healthy, or at least that's what was described earlier?
bored-table-20691
06/03/2021, 6:01 AMkubectl describe deployment
shows - there is no update to the deploymentbillowy-army-68599
06/03/2021, 6:01 AMbored-table-20691
06/03/2021, 6:03 AMbillowy-army-68599
06/03/2021, 6:03 AMbored-table-20691
06/03/2021, 6:04 AMserviceAccount
and serviceAccountName
, it does what I expectkubectl edit
steep-toddler-94095
06/03/2021, 6:35 AMupdating. [diff: ~spec]; [1/2] Waiting for app ReplicaSet be marked available (1/1 Pods available)
I ran a pulumi refresh
to get around the issue (edit: on second thought perhaps the refresh was not needed after the pulumi up
that I needed to manually interrupt, but it's late so i'm not going to re-test until tomorrow). this may warrant a bug ticket filedbored-table-20691
06/03/2021, 6:44 AMsteep-toddler-94095
06/03/2021, 6:46 AMbored-table-20691
06/03/2021, 6:48 AM