My

Component

usage looks like:

export const certManager = new CertManager(
  'certmanager',
  {
    cloudflareApiKey: new Config('cloudflare').require('apikey'),
    email: output(stack.identity.getOutput('email')),
    namespace,
    staging: new Config('certmanager').requireBoolean('staging'),
  },
  opts({ dependsOn: [clusterAdminBinding, namespace] }),
)

It is erroring on these specific dependencies. Both dependencies can be created fine. Do I need to propagate the

dependsOn

inside my

Component

definition to every child?

Component

gist https://gist.github.com/rosskevin/1049072e89ee1428a9cbd7eb0334de73

I printed my resolved

opts

just to be sure, they look good to me:

options: { providers:
       { kubernetes:
          Provider {
            __pulumiResource: true,
            __providers: {},
            __protect: false,
            urn: [OutputImpl],
            id: [OutputImpl],
            cluster: [OutputImpl],
            context: [OutputImpl],
            kubeconfig: [OutputImpl],
            namespace: [OutputImpl],
            __pulumiCustomResource: true } },
      dependsOn:
       [ ClusterRoleBinding {
           __pulumiResource: true,
           __providers: {},
           __protect: false,
           urn: [OutputImpl],
           id: [OutputImpl],
           apiVersion: [OutputImpl],
           kind: [OutputImpl],
           metadata: [OutputImpl],
           roleRef: [OutputImpl],
           subjects: [OutputImpl],
           __pulumiCustomResource: true,
           __inputs: [Object] },
         Namespace {
           __pulumiResource: true,
           __providers: {},
           __protect: false,
           urn: [OutputImpl],
           id: [OutputImpl],
           apiVersion: [OutputImpl],
           kind: [OutputImpl],
           metadata: [OutputImpl],
           spec: [OutputImpl],
           status: [OutputImpl],
           __pulumiCustomResource: true,
           __inputs: [Object] } ] }

work around is to depend on a specific resource in your component that you care about.

@important-leather-28796 it sounds like you’re having trouble with resources inside the component starting to create before the resources listed in the component’s

dependsOn

are ready

Is that right?

I just noticed the console printout to be missing my component at the top, it is pictured associated with a stack

Oh interesting

That is very strange.

tree looks good now. Is there a bug to follow on the depends? I’ll just create a helper for now to propagate them

Didn’t seem to matter. Chaining my

dependsOn

yields the same errors.

I’d understand if I messed up the cluster role binding, but the namespace is a no-brainer.

inside the component it is destructured:

const { cloudflareApiKey, email, namespace: namespaceObject, staging = false } = args
    const namespace = namespaceObject.metadata.name

and I added

dependsOn: [namespaceObject, crds]

to the chart

it does seem to resolve correctly as indicated by the retry message

i’ll change the namespace name to static just for kicks - that is a stack name at the moment

Although it feels like that should just create stuff in

default

namespace and not complain about not finding

development

namespace.

I’ll try the workaround from 217, also following https://github.com/pulumi/pulumi-kubernetes/issues/415#issuecomment-469118560

adding a transform to the helm chart for namespaces had no effect

it is clear to me that the namespace

development

exists, I need to look again at permissions or something else.

I’ll pick this up tomorrow, approach is to go god-mode on permissions and see if things start working….then back up from there. The namespace exists, so something else is up.