kustomize | Customization of kubernetes YAML configurations

Changing the IngressRoutes .spec.routes[0].services[0].name is possible with Kustomize using a NameReference transformer (see docs here) - luckily I found inspiration in this issue. Therefore we need to include the configurations keyword in our kustomize.yaml:

The issue I was experiencing is explained in the strategic merge patch docs;

In the standard JSON merge patch, JSON objects are always merged but lists are always replaced. Often that isn't what we want.

To solve this problem, Strategic Merge Patch uses the go struct tag of the API objects to determine what lists should be merged and which ones should not.

That is why it works to add additional containers (if you use different names for the containers you want to append) with patchesStrategicMerge.

However, the objects and lists I was trying to append items to, were not setup that way and was therefor just replaced.

Since I'm not in a position to change the setup, the solution for me was to resort to patchesJson6902.

patch.yaml

Well, I managed to resolve this. I was using the wrong command to get the digest.

Isn't that what post-renderers are for?

See https://helm.sh/docs/topics/advanced/#post-rendering

A post-renderer can be any executable that accepts rendered Kubernetes manifests on STDIN and returns valid Kubernetes manifests on STDOUT. It should return an non-0 exit code in the event of a failure. This is the only "API" between the two components. It allows for great flexibility in what you can do with your post-render process.

A post renderer can be used with install, upgrade, and template. To use a post-renderer, use the --post-renderer flag with a path to the renderer executable you wish to use:

$ helm install mychart stable/wordpress --post-renderer ./path/to/executable

I haven't used it myself yet, but it looks interesting if you want to run your own alternative kustomize.

See https://github.com/vmware-tanzu/carvel-ytt/tree/develop/examples/helm-ytt-post-renderer for an example that is not kustomize.

For earlier version of kubectl, there was no such way of doing it and there was an issue related to it: https://github.com/kubernetes-sigs/kustomize/issues/1424

But it has been fixed recently and it seems starting from 1.24 we might be able to get the version by just doing kubectl version.

For the older clients, you can find that it is documented in the kustomize's README here: https://github.com/kubernetes-sigs/kustomize#kubectl-integration

There's an open PR to add support for arbitrary YAML in the values field. If merged, I would expect it to be available in 2.4. Reviews/testing are appreciated if you have time!

One workaround is to use the parameters field and set parameters individually. It's not ideal, but maybe could help until 2.4 is released.

You can try using https://kubectl.docs.kubernetes.io/references/kustomize/kustomization/replacements/

For your scenario, if you want to reference the aws-region into your Service labels. You need to create a replacement file.

replacements/region.yaml

I fixed it by changing uses value to

• uses: google-github-actions/setup-gcloud@master

Argo Workflows automatically adds the name of the Cron Workflow as a label on the workflow. That label is accessible as a variable.