gorgeous-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…little-cartoon-10569
05/28/2021, 1:13 AMgorgeous-minister-41131
05/28/2021, 1:15 AMpulumi:pulumi:Stack eks-py-cute-krill
= └─ kubernetes:apps/v1:DaemonSet kube-proxy import [diff: -metadata,spec]; 1 warning
Diagnostics:
kubernetes:apps/v1:DaemonSet (kube-proxy):
warning: inputs to import do not match the existing resource; importing this resource will fail
little-cartoon-10569
05/28/2021, 1:22 AMpulumi import
rather than writing your own code, then Pulumi should populate all the required fields.gorgeous-minister-41131
05/28/2021, 1:27 AM⟩ p import kubernetes:apps/v1:DaemonSet kube-proxy kube-system/kube-proxy
Creating pulumi_pulumi_run ... done
Type Name Plan
pulumi:pulumi:Stack eks-py-cute-krill
= └─ kubernetes:apps/v1:DaemonSet kube-proxy import
Resources:
= 1 to import
8 unchanged
... then produced code output
little-cartoon-10569
05/28/2021, 2:09 AMgorgeous-egg-16927
05/28/2021, 4:02 PMAnyone have any suggestions or best practices for having pulumi edit an existing resource in an k8s/EKS cluster?This feature is tracked in https://github.com/pulumi/pulumi-kubernetes/issues/264
gorgeous-minister-41131
05/28/2021, 6:26 PM