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
package-authoring
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
brief-jelly-98203
09/16/2022, 10:28 PMHey y'all, I am creating a bunch of resources through a kubernetes helm chart with pulumi but for some reason it created them the first time but on subsequent runs it wants to create the resources again (these come from the cert manager and rancher helm charts). Is there a way to mark them as created? I tried refresh but it still wants to create them on subsequent
pulumi upThese are the resources. I confirmed they already exists.
s
stocky-restaurant-98004
09/16/2022, 10:53 PMDo the resources show in
pulumi stackpulumi upb
brief-jelly-98203
09/17/2022, 1:30 AMI just ran it, yes they show there
well, I seem to have tracked this to only service accounts
seems k3s is not giving pulumi info about the creation so it takes them as missing
I have to run refresh
* resource XXX, but the Kubernetes API server reported that it failed to fully initialize or become live: Timeout occurred polling for 'XXX's
stocky-restaurant-98004
09/17/2022, 2:26 PMCan you file an issue for this in pulumi-kubernetes with a minimal program to reproduce? This sounds like a bug, or at least some missing documentation.
f
fresh-carpet-17788
09/22/2022, 1:48 PMHey @brief-jelly-98203, did you resolve this issue by any chance?