No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Not using the same provider. But if you're prepared to manage two stacks, you could create the k8s provider in a conditional guarded by the stack name.

```var k8sProv;
if (Pulumi.getStack() === "k8sYaml") {
  k8sProv = new k8s.Provider("k8s-yaml-renderer", {
    renderYamlToDirectory: "yaml",
  });
} else {
  k8sProv = new k8s.Provider("k8s-yaml-renderer", {});
}```

Why render it and apply as a ConfigFile instead of applying directly? If you're trying to change the Pulumi apply behaviour, it's better to apply the noAwait annotation than what you're describing.  

This is more just informational, sometimes its nice to look at the YAML before it gets applied. I'm teaching folks Kubernetes at my company and this provides them a better understanding