Fixed
#2926 Use client-side create for new resources instead of server-side apply.
Users may observe stricter errors on some Create operations. Please read carefully.
When a resource already exists in the cluster, the API server now returns an AlreadyExists error instead of silently updating the existing object. This prevents data loss from create-then-delete scenarios (e.g. renaming a Pulumi resource or replacing an explicitly-named resource). A new provider config option upsertExistingObjects (default false) restores the previous upsert behavior for users who intentionally adopt existing cluster resources. To manage fields on existing objects without owning their lifecycle, use Patch resources (e.g. NamespacePatch).
Added
#2280 Add enablePatchForce provider config option to force SSA patch conflicts on a per-stack basis.
Changed
Upgrade Kubernetes schema and libraries to v1.35.3.