This message was deleted.

Can I create a CRD and use it in the same

pulumi up

run ? I created a

helm.v3.Release

for cert-manager, and a

yaml.v2.ConfigGroup

that defines a

ClusterIssuer

(cert-manager helm release installs the

ClusterIssuer

CRD) . I have a.

depends_on

in the ConfigGroup to wait for the cert-manager helm release to complete. But it seems that pulumi tries to determine if

ClusterIssuer

is a namespaced or not before the helm release actually installed the CRD. (

Exception: marshaling properties: awaiting input property "resources": failed to determine if the following GVK is namespaced: <http://cert-manager.io/v1|cert-manager.io/v1>, Kind=ClusterIssuer

) I've created a https://github.com/pulumi/pulumi-kubernetes/issues/3176 but then I realized that maybe this known already ? or there is another way to make it wait?

Pulumi is really slow. Would using local state improve things? Is there a way to profile the

pulumi up

?

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.