https://pulumi.com logo
#kubernetes
Title
# kubernetes
r

rough-oxygen-8318

12/23/2020, 3:53 AM
I think this is currently not possible but I want to be sure 100%, not sure if I missing something. Is there a way to
monkey patch
kubernetes resources that were not created with Pulumi? My use case is: Adding the environment variable
AWS_VPC_K8S_CNI_CUSTOM_NETWORK_CFG=true
for DaemonSet
aws-node
inside an AWS EKS Cluster (Step 3 in custom-networking AWS Documentation https://docs.aws.amazon.com/eks/latest/userguide/cni-custom-network.html)
p

prehistoric-kite-30979

12/23/2020, 10:42 AM
I'm also interested in this but I couldn't find a way to do it natively. If you can programmatically get the kubeconfig you can probably do it via the kube client libs. My use case is patching coredns to run on fargate.
r

rough-oxygen-8318

12/23/2020, 5:39 PM
Yes, I was thinking something similar. This is going to be my approach: • I'm going to use the official python k8s client to delete the original
aws-node
installation (ClusterRole, ClusterRoleBinding, ServiceAccount, etc) • I found an official helm repo with multiple EKS related charts. I'm going to use pulumi + helm to install the
aws-vpc-cni
(a.k.a
aws-node
) chart. I hope using this installation method give me more flexibility for future upgrades.
10 Views