Channels
pulumi-ai
package-authoring
pulumi-cdk
oracle-cloud-infrastructure
learn-pulumi-events
linen
registry
built-with-pulumi
pulumi-cloud
contribex
testingtesting321
hacktoberfest
cloudengineering
yaml
pulumi-crosscode
content-share
finops
multi-language-hackathon
office-hours
workshops
blog-posts
localstack
welcome
gitlab
pulumi-kubernetes-operator
jobs
aws
pulumi-deployments
dotnet
golang
announcements
java
pulumiverse
python
install
getting-started
cloudengineering-support
testingtesting123
hackathon-03-19-2020
typescript
google-cloud
contribute
azure
kubernetes
docs
automation-api
status
general
Powered by
Title
b
billowy-army-68599
10/12/2022, 6:07 PM
my suspicion here is that the coredns deployment never starts because it’s not tolerating the fargate nodes
h
hundreds-yacht-71603
10/12/2022, 6:08 PM
You are correct. The default annotation has a compute-type: ec2. But ... well isn't that why the kubectl patch is run in the first place?
b
billowy-army-68599
10/12/2022, 7:19 PM
hmm yes. can you open an issue in
github.com/pulumi/pulumi-eks
a
average-pilot-3793
01/06/2023, 10:43 AM
any update on this?
the only WA that I found which is really weird is to do a pulumi up with
aws.eks.Addon
then delete the coredns addon resource, then do a pulumi up again ???
#general
Join Slack