white-balloon-205
gorgeous-egg-16927
01/02/2020, 9:56 PMbusy-umbrella-36067
01/02/2020, 11:05 PMpreview/update
busy-umbrella-36067
01/02/2020, 11:05 PMbusy-umbrella-36067
01/03/2020, 12:13 AMhundreds-portugal-17080
01/03/2020, 6:43 PMrhythmic-hair-33677
01/05/2020, 8:49 AMrhythmic-hair-33677
01/05/2020, 9:30 AMrhythmic-hair-33677
01/05/2020, 9:30 AMsticky-lighter-73941
01/07/2020, 2:02 PMbusy-umbrella-36067
01/07/2020, 11:31 PMkubeconfig
anywhere, only grabbing from eks.Cluster.provider
Error: invocation of kubernetes:yaml:decode returned an error: unable to load Kubernetes client configuration from kubeconfig file: invalid configuration: no configuration has been provided
at monitor.invoke (/root/project/node_modules/@pulumi/pulumi/runtime/invoke.js:172:33)
at Object.onReceiveStatus (/root/project/node_modules/grpc/src/client_interceptors.js:1210:9)
at InterceptingListener._callNext (/root/project/node_modules/grpc/src/client_interceptors.js:568:42)
at InterceptingListener.onReceiveStatus (/root/project/node_modules/grpc/src/client_interceptors.js:618:8)
at callback (/root/project/node_modules/grpc/src/client_interceptors.js:847:24)
limited-rainbow-51650
01/09/2020, 2:01 PMkubernetesx.PodBuilder(...).asStatefulSetSpec()
, is there support to get my volumeClaimTemplates
in the spec?limited-rainbow-51650
01/09/2020, 2:16 PMnice-guitar-97142
01/09/2020, 4:00 PMprovider
argument of CustomResourceOptions
.
const k8sProvider = new k8s.Provider('k8sProvider', {
kubeconfig: k8sCluster.kubeConfigRaw
})
This has been working fine, until i made a config change on the aks cluster where the cluster needed to be destroyed and recreated. The new aks instance was created successfully; however, the kubernetes resources were not updated to use the new provider. I have dealt with this in the past by exporting the stack config, manually editing all of the resources to use the new provider, then importing the stack config and running pulumi up. Am I doing something wrong in how i specify the provider on the resources, or is this a limitation of pulumi?adamant-postman-86832
01/16/2020, 10:02 AMorange-ghost-99337
01/17/2020, 8:44 AMorange-ghost-99337
01/17/2020, 9:05 AMelegant-dress-88912
01/17/2020, 9:10 AMServiceAccount
orange-ghost-99337
01/17/2020, 9:23 AMelegant-dress-88912
01/17/2020, 9:24 AMorange-ghost-99337
01/17/2020, 9:31 AMlate-printer-99022
01/17/2020, 10:13 AMbetter-rainbow-14549
01/17/2020, 3:27 PMhandsome-actor-1155
01/17/2020, 10:44 PMcold-coat-35200
01/20/2020, 2:51 PMyaml.ConfigGroup
yaml
field does not accept Pulumi.Input<string>
? This way I'm unable to pass a string created from an output, for example from a secretcold-coat-35200
01/21/2020, 11:20 AMbroad-helmet-79436
01/22/2020, 9:49 AMbroad-helmet-79436
01/22/2020, 9:49 AMbroad-helmet-79436
01/22/2020, 9:49 AMmany-lock-25065
01/27/2020, 3:18 PMpulumi up
. Instead, we need one pulumi up
where the import
simply reflects the existing resource, and then another one where we edit the code to change the resource. We've verified this multi-stage flow works, but it feels clunky (currently we have to manually edit the code between the first and second pulumi up). Are there any tricks we can use to combine into a single stage?
One thought was that maybe there is a variable that denotes whether or not the resource is already referenced. Then we could run pulumi twice, and use a switch statement to distinguish the two cases. Feels very hacky though.