Documentation on SSA preview is incorrect

[rquitales]

What happened?

https://www.pulumi.com/registry/packages/kubernetes/how-to-guides/managing-resources-with-server-side-apply/#prerequisites

The above documentation implies that a provider with SSA enabled will always perform an input diff (which is what's done for a provider configured to use CSA). This is incorrect as a SSA enabled provider will always perform a server-side dry-run for preview. The following are scenarios of when client-side or server-side dry-run is used:

Server-side dry-run:

• Kubernetes provider with enableServerSideApply set to true

Client-side dry-run (ie. input diff);

• Kubernetes provider with enableServerSideApply set to false
• Kubernetes provider with enableServerSideApply set to true AND server-side dry-run fails due to lack of PATCH permissions

Example

Output of pulumi about

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

[EronWright]

Note also that the CSA-to-SSA migration logic doesn't take effect during a preview, and this may lead to spurious "conflict" messages during preview.