renderYamlToDirectory is still dependent on a kubernetes cluster connection

[trondhindenes]

What happened?

There are several situations where pulumi errors when using renderYamlToDirectory - althought it's supposed to be a completely "offline" way to generate kubernetes manifests:

If the "KUBECONFIG" environment variable is set (a very common way of pointing kubectl to a config), pulumi errors out:

error: pulumi:providers:kubernetes resource 'minioProvider': property kubeconfig value {<path-to-kubeconfig-file>} has a problem: "kubeconfig" arg is not compatible with "renderYamlToDirectory" arg

if the active kubeconfig is pointing at a cluster that is not reachable for some reason (for example, expired credentials): This does not cause errors, but the error from kubeconfig is printed, so it's a clear indication that pulumi attempts to communicate with the configured cluster

Example

See above

Output of pulumi about

CLI          
Version      3.136.1
Go Version   go1.23.2
Go Compiler  gc

Plugins
KIND      NAME        VERSION
resource  kubernetes  4.21.1
language  nodejs      unknown

Additional context

When using renderYamlToDirectory, pulumi should avoid any cluster communication using kubectl.

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).

[rquitales]

Thanks for reporting this issue @trondhindenes and apologies that you're facing it. Please note that rendYamlToDirectory support is still a beta feature. We'll add this to our backlog to further investigate and resolve.

[trondhindenes]

thanks!