Pulumi Kubernetes v4.34.0: CRDs as provider extensions

Pulumi Kubernetes provider v4.34.0 adds enhanced Custom Resource Definition support, including a new `--extension` option that lets users generate typed SDKs for any CRD from its manifest and extend an existing Kubernetes provider instance without separate configuration or kubeconfig files. The release also includes Kubernetes v1.37.0 resources, dependency updates, and bug fixes, while addressing growing use of CRD-based technologies such as the Gateway API, now recommended for cluster ingress following ingress-nginx’s retirement. Generated CRD SDKs can be regenerated as dependencies through `pulumi install`, optionally versioned or committed to source control, and used across all Pulumi-supported languages, including YAML, with validated types and autocomplete support. Users of crd2pulumi can migrate by updating their SDK package reference without changing stack state, with upgrades expected to produce no changes during `pulumi up`; the feature requires Pulumi v3.255.0 and Kubernetes provider v4.34.0.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.