cool-egg-85210/03/2019, 10:09 PM
gentle-diamond-7014710/03/2019, 10:17 PM
cool-egg-85210/03/2019, 10:18 PM
gentle-diamond-7014710/03/2019, 10:21 PM
cool-egg-85210/03/2019, 10:21 PM
colossal-beach-4752710/03/2019, 10:22 PM
cool-egg-85210/03/2019, 10:22 PM
colossal-beach-4752710/03/2019, 10:28 PM
cool-egg-85210/03/2019, 10:28 PM
pulumi preview -s LinioIT/support --tracing=file:/out.trace
brash-plastic-6579710/04/2019, 2:50 PM
calls to Kubernetes are (a) taking more time than expected and (b) being done serially. We should be able to improve on both of these.
cool-egg-85210/04/2019, 8:41 PM
operations against your cluster? The fact that all these operations are taking multiple seconds suggests there may be a fundamental issue related to a slow connection to Kubernetes that is accentuating the issue here. (Some of the follow-ups here will hopefully be able to mitigate that - but this could be a contributing factor).
cool-egg-85210/04/2019, 9:19 PM
cool-egg-85210/04/2019, 9:21 PM
That's an order of magnitude faster - which I think is related to why this update time is quite so bad in your case. That said, there are more things Pulumi can do to mitigate here.
$ time kubectl get namespaces NAME STATUS AGE default Active 23d kube-node-lease Active 23d kube-public Active 23d kube-system Active 23d myns-mn0bllwq Active 16d real 0m0.132s user 0m0.087s sys 0m0.019s
cool-egg-85210/04/2019, 9:26 PM
gorgeous-egg-1692710/10/2019, 7:58 PM
cool-egg-85210/10/2019, 8:02 PM
gorgeous-egg-1692710/10/2019, 8:04 PM