This message was deleted.
# kubernetes
s
This message was deleted.
p
i’m really new to pulumi but it looks like we’d need some awaiter for that or similar stuff? Or am just missing something simple? :D
q
Can I ask, why do you need the token?
p
Hey, ofc. I have couple use-cases for multi-cluster deployments as described for example here: https://istio.io/latest/docs/setup/install/multicluster/multi-primary/#enable-endpoint-discovery or here: https://docs.solo.io/gloo-edge/master/guides/gloo_federation/cluster_registration/ I hope I am not abusing pulumi to do that 😅
q
Interesting use case. There's not really a nice way to handle that with Pulumi specific code - because there's no guarantees when the token will be added / the secret created. You can add a generic Kubernetes client and add a reflector though?
p
there’s no guarantees when the token will be added
actually, it’s immediate so it’s enough to fetch resource from API - for example this works in terraform because they always read created resource😅 So i was wondering if it’s possible to do some refresh or something similar also here. But yeah, gonna give a shot to kube client. Thank you :)
g
You should be able to run a
pulumi refresh
after the creation, but I can’t think of a way to do this in one step currently. Here’s the issue tracking this class of problems: https://github.com/pulumi/pulumi-kubernetes/issues/1260
👀 1