Add kustomization.yaml

[jwenz723]

I am trying to install the AWS VPC CNI with CNI Custom Networking feature enabled. I would like to be able to create a kustomize patch and apply it to the config/v1.5/aws-k8s-cni.yaml file without having to copy and paste the config/v1.5/aws-k8s-cni.yaml file into my repo (so that no one can make modifications to it from my org).

There is a way to accomplish this using the go-getter generator plugin as described here, but it would be nicer if the amazon-vpc-cni-k8s repo just contained a kustomization.yaml file so it could be referenced directly as a kustomize base/resource without the need for a custom generator plugin.

This would allow for my kustomization.yaml file to look something like this to apply my patch for CNI Custom Networking:

patchesStrategicMerge:
  - aws-node-patch.yaml

resources:
- github.com/aws/amazon-vpc-cni-k8s//config/v1.5?ref=v1.5.4 // this assumes that there is a kustomization.yaml file within the config/v1.5 directory

[jaypipes]

Related: #758

Hi @jwenz723! Our long-term plan is to get rid of the versioned subdirectories under /config and use a single daemonset.yaml file (possibly using kustomize). Also, per #758, our best practice is standardizing around Helm charts for deploying the CNI.

I think supporting Kustomize is a good idea and something we should look at once we move to a single config/ directory.

[jwenz723]

A helm chart could likely work for what I do. Thanks for the update.

[mogren]

Helm charts: https://github.com/aws/eks-charts/tree/master/stable/aws-vpc-cni