ci: enable k8s specific validations

[v1v]

What

As requested, let's enable the k8s specific builds in the CI

Actions

• Delete the Jenkinfile.yml file
• What's the list of supported versions to be tested? (At the moment only one for simplicity)
• When to run (at the moment always)?
• Copy the required scripts from .ci/scripts (.ci/scripts/kind-setup.sh, .ci/scripts/install-kind.sh and .ci/scripts/install-kubectl.sh)

@narph , can you help with the above actions?

Follow ups

• Support when to run to be based on the change-set?
• Shared library step in the Jenkins to configure kind and kubectl?

[narph]

What's the list of supported versions to be tested? (At the moment only one for simplicity)

I see in the old config there are a few k8sTest: "v1.23.0,v1.22.0,v1.21.1,v1.20.7,v1.19.11,v1.18.19", can we pick a few of those?

[v1v]

@narph , it works but there are failures with the project:

[2022-01-27T16:41:20.613Z] + make -C deploy/kubernetes test
[2022-01-27T16:41:20.613Z] make: Entering directory '/var/lib/jenkins/workspace/gent_elastic-agent-poc-mbp_PR-19/src/github.com/elastic/elastic-agent-poc/deploy/kubernetes'
[2022-01-27T16:41:20.613Z] Generating elastic-agent-standalone-kubernetes.yaml
[2022-01-27T16:41:20.613Z] Generating elastic-agent-managed-kubernetes.yaml
[2022-01-27T16:41:20.613Z] for FILE in elastic-agent-managed-kubernetes.yaml elastic-agent-standalone-kubernetes.yaml; do \
[2022-01-27T16:41:20.613Z] 	BEAT=$(echo $FILE | cut -d \- -f 1); \
[2022-01-27T16:41:20.613Z] 	kubectl create -f $FILE; \
[2022-01-27T16:41:20.613Z] done
[2022-01-27T16:41:20.874Z] daemonset.apps/elastic-agent created
[2022-01-27T16:41:20.874Z] clusterrolebinding.rbac.authorization.k8s.io/elastic-agent created
[2022-01-27T16:41:20.874Z] rolebinding.rbac.authorization.k8s.io/elastic-agent created
[2022-01-27T16:41:20.874Z] rolebinding.rbac.authorization.k8s.io/elastic-agent-kubeadm-config created
[2022-01-27T16:41:20.875Z] clusterrole.rbac.authorization.k8s.io/elastic-agent created
[2022-01-27T16:41:20.875Z] role.rbac.authorization.k8s.io/elastic-agent created
[2022-01-27T16:41:20.875Z] role.rbac.authorization.k8s.io/elastic-agent-kubeadm-config created
[2022-01-27T16:41:20.875Z] serviceaccount/elastic-agent created
[2022-01-27T16:41:21.137Z] configmap/agent-node-datastreams created
[2022-01-27T16:41:21.137Z] Error from server (AlreadyExists): error when creating "elastic-agent-standalone-kubernetes.yaml": daemonsets.apps "elastic-agent" already exists
[2022-01-27T16:41:21.137Z] Error from server (AlreadyExists): error when creating "elastic-agent-standalone-kubernetes.yaml": clusterrolebindings.rbac.authorization.k8s.io "elastic-agent" already exists
[2022-01-27T16:41:21.137Z] Error from server (AlreadyExists): error when creating "elastic-agent-standalone-kubernetes.yaml": rolebindings.rbac.authorization.k8s.io "elastic-agent" already exists
[2022-01-27T16:41:21.137Z] Error from server (AlreadyExists): error when creating "elastic-agent-standalone-kubernetes.yaml": rolebindings.rbac.authorization.k8s.io "elastic-agent-kubeadm-config" already exists
[2022-01-27T16:41:21.137Z] Error from server (AlreadyExists): error when creating "elastic-agent-standalone-kubernetes.yaml": clusterroles.rbac.authorization.k8s.io "elastic-agent" already exists
[2022-01-27T16:41:21.137Z] Error from server (AlreadyExists): error when creating "elastic-agent-standalone-kubernetes.yaml": roles.rbac.authorization.k8s.io "elastic-agent" already exists
[2022-01-27T16:41:21.137Z] Error from server (AlreadyExists): error when creating "elastic-agent-standalone-kubernetes.yaml": roles.rbac.authorization.k8s.io "elastic-agent-kubeadm-config" already exists
[2022-01-27T16:41:21.137Z] Error from server (AlreadyExists): error when creating "elastic-agent-standalone-kubernetes.yaml": serviceaccounts "elastic-agent" already exists
[2022-01-27T16:41:21.137Z] make: *** [Makefile:9: test] Error 1

[2022-01-27T16:41:21.137Z] make: Leaving directory '/var/lib/jenkins/workspace/gent_elastic-agent-poc-mbp_PR-19/src/github.com/elastic/elastic-agent-poc/deploy/kubernetes'

script returned exit code 2

I assume those errors are not related to this particular change but the source code.