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

*Access to outputs from K8s `CustomResource`*?

We're using code like the following to provision a custom resource. The issue that we're seeing is that `foo.status` is not defined so we cannot `.apply()` on it.

```foo = CustomResource(
    "foo-sslcerts",
    api_version="<http://networking.gke.io/v1|networking.gke.io/v1>",
    kind="ManagedCertificate",
    metadata={
        "name": "foo-sslcerts",
        "annotations": {"<http://pulumi.com/patchForce|pulumi.com/patchForce>": "true"},
    },
    spec={
        "domains": ["<http://www.foo.net|www.foo.net>"],
    },
)
...
bar = CustomResource(
    "bar-sslcerts",
    api_version="<http://networking.gke.io/v1|networking.gke.io/v1>",
    kind="ManagedCertificate",
    metadata={
        "name": "bar-sslcerts",
        "annotations": {"<http://pulumi.com/patchForce|pulumi.com/patchForce>": "true"},
    },
    spec={
        "domains": foo.status.apply(lambda x: compute_bar_domains(x)),
    },
)```
This happens despite `"status"` showing up in the `"outputs"` section of the state file for the `foo-sslcerts` resource. That is, if we remove the entire `bar` section, run `pulumi up`, and then run `pulumi stack export` we can see the outputs for `foo-sslcerts`, which include `"status"`.

This is with `pulumi==3.111.1` and `pulumi-kubernetes==4.9.1`.