early-musician-4164510/31/2018, 9:05 PM
? I couldn't find the possible values from a cursory look at https://github.com/pulumi/pulumi-kubernetes/blob/master/sdk/nodejs/helm.ts
is currently required, but probably shouldn't be as Helm doesn't require the version. Opened https://github.com/pulumi/pulumi-kubernetes/issues/255 to track, and you can should be able to work around in the meantime by passing
early-musician-4164510/31/2018, 10:13 PM
instead of an
? meaning, if something already exists in kubernetes then we just ignore it as if we were doing
helm upgrade -i
Updating (poc): Type Name Status Info pulumi:pulumi:Stack eks-cluster-poc + ├─ kubernetes:helm.sh:Chart aws-k8s-cni created + │ └─ kubernetes:core:ServiceAccount kube-system/aws-node **creating failed** 1 error ~ └─ kubernetes:helm.sh:Chart splunk-forwarder updated [diff: -version] Diagnostics: kubernetes:core:ServiceAccount (kube-system/aws-node): error: Plan apply failed: serviceaccounts "aws-node" already exists
and does a no-op
to look up a resource if already there, instead of attempting to recreate it. I suspect there's a reason why that doesn't make sense in your scenario, but curious to understand more.
early-musician-4164510/31/2018, 10:26 PM
example I can use?
import * as k8s from "@pulumi/kubernetes"; const serviceaccount = k8s.core.v1.ServiceAccount.get("aws-node", "kube-system/aws-node"); export const serviceaccountSercrets = serviceaccount.secrets;