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, I'm new to IaC, and I'm spinning up an EKS stack on AWS. I just want to make sure I need two separate stacks: one to manage Kubernetes and the nodes/pods and one to manage the EKS configuration on the AWS side of things. I'm also struggling to find documentation relating to deploying a service mesh using Pulumi

You don't _need_ to, but there are benefits to doing it this way.

Separating your base infra from your app-specific infra generally makes things easier to grok. Often aligns along team boundaries too.

Alright, understood! I will keep both projects separate.