Explicitly set kind version when running tests in CI

[swiatekm]

Up until now we depended on the kind version shipped by Github, which opened us up to unexpected breakage whenever they upgraded. This has happened recently with an upgrade from 0.19.0 to 0.20.0.

This change:

• explicitly sets the kind version in CI
• updates Node images for kind 0.20.0
• uses kind 0.17.0 to run tests for K8s <1.21, which kind 0.20.0 doesn't support out of the box
• updates kuttl to the latest released version

[jaronoff97]

Just one thought on how to make this a bit cleaner without env vars.

[jaronoff97]

Instead of adding these to the environment like this, we could use the matrix.include functionality of github actions. https://docs.github.com/en/actions/using-jobs/using-a-matrix-for-your-jobs#expanding-or-adding-matrix-configurations

This would let us specify exactly KIND version each kube version should be using.

[swiatekm]

I considered doing that, but given that:

1. There would only ever be two kind versions
2. There's less duplication this way, you only change the kind version in one place if you want to upgrade

I decided to do it this way. I don't have a strong opinion on it though, the matrix approach is fine.

[pavolloffay]

Nice fix for the CI 🥳

LGTM, but @jaronoff97 has a good comment :)

[pavolloffay]

@swiatekm-sumo should be a similar fix applied to a local setup of kind?

[swiatekm]

@swiatekm-sumo should be a similar fix applied to a local setup of kind?

I think so, but I didn't want to hold this PR up with even more changes. We should treat kind (and kuttl as well) the same way as we treat other local tools - have a make target that installs them to LOCALBIN, and use that binary throughout the Makefile.

[TylerHelmuth]

I view this PR as a temporary solution until we drop 1.19 (and other old versions) entirely. I'm in favor of getting this merged to unblock other work and then quickly bumping our min k8s version.

[pavolloffay]

I am merging this to fix the CI, additional fixes can be submitted in follow up PRs

[pavolloffay]

I view this PR as a temporary solution until we drop 1.19 (and other old versions) entirely

@TylerHelmuth why do you see this as a temporary solution?

[TylerHelmuth]

@pavolloffay I see the permanent solution to be bumping our minimum supported k8s version which I expect to correlate with being able to use a single kind version.