linkerd
Run multicluster tests on min and max k8s versions
This change adds another job in the workflow to run multicluster tests on two separate k8s versions. As part of the change, some just recipes have been added to simplify (where possible) the interaction with the multicluster build process.
Signed-off-by: Matei David [email protected]
I took a pass at this. It's not quite there yet, but may show how we can get closer to ensuring that we setup multiple clusters: https://github.com/linkerd/linkerd2/commit/72d9b4dae590ef15b95305d7d856191ab1d96169
My basic idea is:
- Don't bother creating a new cluster for the 'source' cluster -- just use the default l5d-test cluster (it doesn't need any special configuration)
- Create a target cluster with a load balancer in front of it.
- Use the existing infra to setup the base cluster, and then run a setup of the target cluster by overriding k3d-name and _k3d-flags.
Ok, finished going through ttps://github.com/linkerd/linkerd2/commit/72d9b4dae590ef15b95305d7d856191ab1d96169. The suggestions were great. I copied them over (with minimal changes here and there, e.g when setting the contexts when running mc-test). Thanks for the suggestions!
I've also opened https://github.com/linkerd/linkerd2/pull/9566 for the pause container.
I did some testing locally and came up with a few small suggestions https://github.com/linkerd/linkerd2/pull/9596
Tests failing because of https://github.com/linkerd/linkerd2/pull/9603 most likely