Hi, Anyone have any experience deploying a policy for the kube-descheduler? I'm trying to do so as a pulumi Custom Resource but running into the following error:

creation failed: no matches for kind "DeschedulerPolicy" in version "descheduler/v1alpha2"

And here is my config for the policy:

k8s.apiextensions.CustomResource(
            "descheduler-policy",
            kind="DeschedulerPolicy",
            api_version="descheduler/v1alpha2",
            metadata=k8s.meta.v1.ObjectMetaArgs(
                namespace="kube-system",
            ),
            spec={
                "profiles": [
                    {
                        "name": "default",
                        "pluginConfig": [
                            {
                                "name": "DefaultEvictor"
                            },
                            {
                                "name": "HighNodeUtilization",
                                "args": {
                                        "thresholds": {"cpu": 20, "memory": 30},
                                },
                            },
                        ],
                        "plugins": {
                            "evict": {"enabled": ["DefaultEvictor"]},
                            "balance": {"enabled": ["HighNodeUtilization"]}
                        },
                    }
                ],
            },
            opts=pulumi.ResourceOptions(
                provider=provider,
                depends_on=[
                    cluster,
                    descheduler
                ],
                parent=self,
            ),
        )

have you deployed the custom resource definition?

According to pulumi docs, the Custom Resource is an instance of a CRD, so I thought they were one in the same

not quite. a CRD extends the API inside the Kubernetes API, the Custom Resource is an instance of it

Do you know of any examples of a CRD deploy in pulumi docs? I can only find docs for CR.

@numerous-journalist-43638: DeschedulerPolicy are not a CRD, it's the internal yaml format of the descheduler. You can define them as configmap or use the helm chart value to add them