billowy-vr-96461
05/27/2021, 8:00 PMtall-scientist-89115
05/27/2021, 8:17 PMgorgeous-minister-41131
05/28/2021, 1:07 AMkube-proxy
daemonset that gets deployed to fresh EKS clusters… would I use a get? I presume I’d have to import the resource first…gray-hamburger-90102
05/28/2021, 8:34 AMhundreds-kite-52072
05/28/2021, 11:34 AMrough-window-15889
05/28/2021, 3:39 PMbrash-kite-78002
05/28/2021, 4:02 PMaverage-greece-53878
05/28/2021, 4:41 PMearly-france-31838
05/28/2021, 4:49 PMpolite-continent-12996
05/28/2021, 5:55 PMbusy-cricket-68352
05/28/2021, 8:27 PMgreen-dentist-53234
05/28/2021, 9:50 PMbest-vase-91139
05/29/2021, 5:21 PMdazzling-sundown-39670
05/30/2021, 7:15 PM<http://app.pulumi.com|app.pulumi.com>
?freezing-zoo-29688
05/31/2021, 2:59 AMgcp.container.NodePool
with
management=gcp.container.NodePoolManagementArgs(
auto_repair=False,
auto_upgrade=False
)
But I got an error **creating failed**
* error creating NodePool: googleapi: Error 400: Auto_upgrade and auto_repair cannot be false when release_channel STABLE is set., badRequest
Then I deleted the management and tried to pulumi up
again but I get the error
* googleapi: Error 404: Not found: node pool "dev-preemptible-nodes-8d7b054" not found., notFound
Pulumi didn't create the NodePool and now it is trying to update. How can I force to retry the creation ?elegant-pager-5412
05/31/2021, 5:02 AMpulumi up
. Is there any way we can easily configure it so that Pulumi won’t attempt to delete those? Perhaps there is an easy way to import the configurations instead?curved-pharmacist-41509
05/31/2021, 6:54 AMbroad-dog-22463
05/31/2021, 6:55 AMbroad-dog-22463
05/31/2021, 6:56 AMcurved-pharmacist-41509
05/31/2021, 6:58 AMelegant-pager-5412
05/31/2021, 8:51 AMpulumi up
?great-optician-69584
05/31/2021, 2:43 PMred-football-97286
06/01/2021, 8:17 AMcolossal-vr-62639
06/01/2021, 8:53 AMcolossal-vr-62639
06/01/2021, 8:53 AMwhite-pencil-38837
06/01/2021, 9:03 AMerror: Duplicate resource URN 'urn:pulumi:sbx::k8s-monitoring::kubernetes:<http://helm.sh/v2:Chart$kubernetes:rbac.authorization.k8s.io/v1:Role::monitoring/sbx-kubernetes-monitoring-prometheus';|helm.sh/v2:Chart$kubernetes:rbac.authorization.k8s.io/v1:Role::monitoring/sbx-kubernetes-monitoring-prometheus';> try giving it a unique name
purple-lawyer-35555
06/01/2021, 9:45 AM// pulumi deploys server resources --> Pulumit.output gives me the 'endpoint'
execSync(
pulumi.interpolate`yarn build --env endpoint_url=${endpoint}`
)
// pulumi deploys the frontend resources
ripe-russia-4239
06/01/2021, 3:21 PMOutput
appears to be conceptually the same as a Future, could the Pulumi Output
type (in theory) extend the language's Future equivalent, rather than operating independent of it? In the Node SDK, for example, it would be really nice to be able to await
an Output<T>
like I would a Promise<T>
. I'm also curious about the design decision to use constructors as the provisioning call rather than e.g. a method on the object. As it's all more for my curiosity than anything, I thought I'd ask here rather than on GitHub ☺️rough-window-15889
06/01/2021, 3:43 PMdamp-tiger-87899
06/01/2021, 4:44 PM