Is there any easy way without juggling configs/stacks to be able to deploy pulumi to something locally without it trying to store the state remotely? The example is, we have local kubernetes clusters for dev and I want to configure them with baseline services, such as ingress and databases etc. But it doesn't make sense that it has a remote stack tracking it as it is only needed for each dev locally

not really sure what you want to achieve but if you just want to use pulumi to configure LOCAL k8s cluster, you can use local state backend

Thanks @prehistoric-activity-61023 that's what I suspected. Its just cumbersome as people will need to login and logout depending on what you are doing. The idea is to have consistency with deployments. Whether I deploy yaml/helm to a local env vs our staging and prod. I would prefer it either all uses pulumi or not

do you want to deploy the same project to local envs as well as staging/prod?

Ah awesome, that could actually work nicely. Let me give that a try thanks

see https://www.pulumi.com/docs/reference/cli/environment-variables/ (

PULUMI_BACKEND_URL

)