Open ecerulm opened 3 weeks ago
The workaround I use now is to create the CRDs myself with another kubernetes.yaml.v2.ConfigFile
with just the CRDs
# https://www.pulumi.com/registry/packages/kubernetes/api-docs/yaml/configfile/
crds = kubernetes.yaml.v2.ConfigFile(
"letsencrypt-prod",
file="files/cert-manager.crds.yaml",
opts=pulumi.ResourceOptions(
depends_on=[
],
provider=kubernetes_provider,
),
)
then I set installCRDs: false
for the cert-manager helm values, and make the ClusterIssuer depend on the crds ConfigFile
and cert-manager's Release
What happened?
I'm deploying cert-manager helm release + a ClusterIssuer resource
cert-manager helm release creates the ClusterIssuer CRD, but it seems that the
pulumi.ConfigGroup
that creates theClusterIssuer
resources tries to check some properties of theClusterIssuer
CRD before it's actually created although there isdepends_on
to the cert-manager.If I rerun
pulumi up -y --skip-preview
after then theClusterIssuer
will be created fine. That's why I think it's a timing issue between the creation of theClusterIssuer
CRD and the actualClusterIssuer
resource.Example
Output of
pulumi about
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).