This message was deleted.

`CustomResource`s don’t have built in readiness logic, but the underlying resources of a

ConfigFile

often do (Deployments, Services, etc). https://github.com/pulumi/pulumi-kubernetes/issues/861 is still open, but in the meantime, you can use

dependsOn

with

getResource

as shown here: https://github.com/pulumi/pulumi-kubernetes/blob/0162c7f3ff223c70eb5f29d70cec77d8dbaf52a7/tests/integration/istio/step1/istio.ts#L43-L69

Thank you. I have attempted to use the

getResource

but it appears to be ignored.

// Create TLS secret from sealed secret
const tlsCert = new k8s.yaml.ConfigFile('dev-local-tls', {
  file: '../01-identity/dex/sealed-dev-local-tls.yaml',
})


// SealedSecrets controller will decrypt the above and generate a
// dev-local-tls-ss-test secret in the identity namespace


// In this example this should fail as the sealed-secret will fail to decrypt...
const secret = tlsCert.getResource(
  'v1/Secret',
  'identity',
  'dev-local-tls-ss-test'
)


const next = new k8s.core.v1.Secret('should-wait', {}, { dependsOn: secret })

Is the Secret part of the YAML, or generated by a controller? If it’s generated by a controller, this is a case we don’t have a built-in answer for. You might have a add a polling loop or something to make sure the Secret exists before continuing. Perhaps it would make sense to add optional retries to the

get

operations to make this easier? @white-balloon-205

It is a Bitnami Sealed Secret https://github.com/bitnami-labs/sealed-secrets#sealed-secrets-for-kubernetes The SealedSecret itself has the appropriate events that should be queryable (i.e. failed to decrypt, unsealed, etc) the controller then creates a Secret. It doesn’t appear that CustomResources can be queried with the getResource method (or at least the TS types don’t allow for it). So the approach would be to either query the SealedSecret itself to see if it has an error, or somehow reference the generated secret created by the controller.

Thanks for the info. Would you mind opening an issue on that? I’ve got some ideas on how to make that type of thing easier with pulumi

What is confusing is that in the code example I posted above

const secret = tlsCert.getResource()

seems to be a no-op. I know the resource doesn’t exist. So I would expect anything else that dependsOn it would fail.

I suspect what’s happening in that case is that the return value is

undefined

, and therefore doesn’t actually change the

dependsOn

.

Oh. That makes sense.

The scenario you described with the sealed secrets. Just need more context on what you were expecting vs what actually happened

Will do

That looks great; thanks for writing that up! We’re definitely looking for ways to improve the CRD experience on Pulumi. Most folks are currently writing custom logic in their programs to handle those cases, but I do like the idea of making the provider itself more extensible.