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

Hi all. I have infrastructure separated into `common` (where i create eks cluster and nodepool and shared things else) and per-project infrastructure (lives with code and has services/deployments/etc). How do i specify in the per-project infrastructure which eks cluster to deploy to? i have aws:profile specified in the stack yaml, but it looks that pulumi ignores it and deploys to current kubectl context.

<@U03U4EB8U21> export the kubeconfig from your `common` project, then build a provider in your per-project infrastructure and pass it to the resources.

here’s an example of building the cluster and exporting the kubeconfig: <https://github.com/jaxxstorm/pulumi-examples/blob/main/typescript/aws/eks-platform/eks/index.ts#L22>
then grabbing the provider from the other stack as a stack reference: <https://github.com/jaxxstorm/pulumi-examples/blob/main/typescript/aws/eks-platform/sample-app/index.ts#L8>