Vector: Re-enable kubernetes tests in CI
Currently, we have Kubernetes tests disabled in CI because we were running out of resources and hitting continuous etcdserver timeouts. I suggest we re enable Kubernetes by hosting a small single node cluster somewhere on EC2 that our CI machines can connect too.
LucioFranco
All 3 comments
Moving forward here I think we should attempt to also test against at least three versions of kube. 1.13, 1.14 and the latest version which now is 1.17.
cc @Hoverbear you may have some other ideas as well.
LucioFranco
on 3 Feb 2020
Also, to remove the need for manually updating test image, which is easy to forget, we should locally build an image of tested version of Vector, make it available to Kubernetes cluster, and pass the image name to the tests over environment variable.
ktff
on 27 Feb 2020
@ktff this seems like a somewhat important issue. Would you mind working on re-enabling this? We're also moving towards Github Actions so it might be worth adding it as a Github Action instead of in Circle.
binarylogic
on 27 Feb 2020
Related issues
jhgg
路
4Comments
lewisthompson
路
3Comments
LucioFranco
路
3Comments
LucioFranco
路
3Comments
a-rodin
路
3Comments
Most helpful comment
Also, to remove the need for manually updating test image, which is easy to forget, we should locally build an image of tested version of Vector, make it available to Kubernetes cluster, and pass the image name to the tests over environment variable.