No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Good morning! I’m trying to automate deployment of several steps in EKS, including the creation of a CA, the CSR, and the Kubernetes secret. I see classes like `CertificateSigningRequestConditionArgs` and `CertificateSigningRequestStatusArgs` but have yet to find documentation as to how these tie into a `CertificateSigningRequest` so I can get the Kubernetes secret signed (“Approved,Issued”). Anyone have a pointer to an example?

A related question is how can I get Pulumi to wait on the creation of certain objects, like the keypair?

To partially answer the last question, using this syntax seems to work. I think this is telling Pulumi to fire off the deployment and not wait around for it to succeed, which allows the code elsewhere to finish creating the secret.
```annotations={
  "<http://pulumi.com/skipAwait|pulumi.com/skipAwait>": "true"
}```

Unfortunately, Pulumi complains that the object I want to use isn’t a “resource”.