Second question: I set up a primary project that sets up my k9s clusters. I then set up services. Currently pulumi seems to use whatever is my kubectl config as default config. I tried to generate a kubeconfig as stack output in the cluster project, and then to load it(using stackreference and getting the output of it, then loading it as a provider ressourceoption when creating the namespace). However this somehow doesn't seem to work anymore... Any way to debug what it's actually using for auth?

What exactly doesn't work anymore? The pattern you describe (creating a kubeconfig, exporting it as a stack output, then accessing this output and explicitly instantiating the provider) is quite common and often the most preferable way.

Aha moment. I did not set it everywhere in ressource construction as provider.

As far as I know, that's not possible, because "further operations" is not well-defined

I see. Then copy pasta time for "opts=pulumi.ResourceOptions(provider=k8s_provider)" everywhere

You need to pass the provider to each resource it should be used for, otherwise it falls back to the default provider (if available)

yeah, I thought the default provider could have been changed

You can look into https://www.pulumi.com/docs/concepts/options/providers/ or https://www.pulumi.com/docs/concepts/options/parent/ to define and inherit providers

aha, so it still might be possible to define the parent's provider. probably at the pulumipulumiStack level

I don't think that's possible, as far as I know the pulumipulumiStack resource is a pseudo-resource or placeholder that is the parent to all other resources but cannot be modified

makes sense. I guess the easiest would then just to make all these ressources child to the provider in question