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

Hello!
Did anyone try to use ConfigGroup? For me, it creates empty CRDs from the files I specify...

image.png

```const koptions: eks.KubeconfigOptions = {
    profileName: 'saml'
};



const cluster = new eks.Cluster(
    "aizi-test-cluster",
    {
        providerCredentialOpts: koptions
    }
);


const crds = new k8s.yaml.ConfigFile(
    "prometheusCRDs",
    {
        file: process.cwd() + "/crds-init/prometheus/9.3.1/crd-servicemonitor.yaml",
    },
    {
        provider: cluster.provider
    }
)```


Here you can find the CRD itself <https://raw.githubusercontent.com/coreos/prometheus-operator/release-0.38/example/prometheus-operator-crd/monitoring.coreos.com_servicemonitors.yaml>

I receive the same results for ConfigFile and ConfigGroup.

the file you're linking is a custom resource _definition_ which just registers the definition with the API server

you need to instantiate an instance of that now

you getting an empty list is correct for your command

Hmm, interesting. How should I instantiate it? Thank you for your help!

use this to create a "service monitor"
<https://www.pulumi.com/docs/reference/pkg/kubernetes/apiextensions/customresource/>

Uff, sorry! I basically executed the wrong CLI command. Sorry, for taking your time. I should have checked the stack to be sure.

Everything works fine. I've just made a silly mistake!