Channels
announcements
automation-api
aws
azure
blog-posts
built-with-pulumi
cloudengineering
cloudengineering-support
content-share
contribex
contribute
docs
dotnet
finops
general
getting-started
gitlab
golang
google-cloud
hackathon-03-19-2020
hacktoberfest
install
java
jobs
kubernetes
learn-pulumi-events
linen
localstack
multi-language-hackathon
office-hours
oracle-cloud-infrastructure
plugin-framework
pulumi-ai
pulumi-cdk
pulumi-cloud
pulumi-crosscode
pulumi-deployments
pulumi-kubernetes-operator
pulumiverse
python
registry
status
testingtesting123
testingtesting321
typescript
welcome
workshops
yaml
Title
b
billions-hospital-77217
12/21/2021, 12:56 AMHi, 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
l
little-cartoon-10569
12/21/2021, 12:57 AMYou 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.
b
billions-hospital-77217
12/21/2021, 12:59 AMAlright, understood! I will keep both projects separate.