Support 1.17.12-20201117 EKS AMI

[christianAckman]

Describe the bug

Similar to this issue: #1335

Falco pods are crashing due to trying to reach nonexistent driver module.

I can see there was a commit for this version: here

But not seeing the published module: here

* Setting up /usr/src links from host
* Running falco-driver-loader with: driver=module, compile=yes, download=yes
* Unloading falco module, if present
* Trying to dkms install falco module
* Running dkms build failed, couldn't find /var/lib/dkms/falco/85c88952b018fdbce2464222c3303229f5bfcfad/build/make.log
* Trying to load a system falco driver, if present
* Trying to find locally a prebuilt falco module for kernel 4.14.203-156.332.amzn2.x86_64, if present
* Trying to download prebuilt module from https://dl.bintray.com/falcosecurity/driver/85c88952b018fdbce2464222c3303229f5bfcfad/falco_amazonlinux2_4.14.203-156.332.amzn2.x86_64_1.ko
curl: (22) The requested URL returned error: 404 Not Found
Download failed, consider compiling your own falco module and loading it or getting in touch with the Falco community

How to reproduce it

Update AMI in EKS to 1.17.12-20201117 and install Falco
Watch it fail with kubectl get pods

Expected behaviour

Falco should be in Running status, but instead it gets stuck in a CrashLoopBackOff

Environment

Falco version: 0.24.0
Cloud provider or hardware configuration: EKS cluster (1.17)
OS: Amazon Linux 2
Installation method: helm install

[christianAckman]

this is fixed by upgrading to version 0.26.2

driver will pull from falco instead of bintray: https://download.falco.org/driver/2aa88dcf6243982697811df4c1b484bcbe9488a2/falco_amazonlinux2_4.14.203-156.332.amzn2.x86_64_1.ko