Update k8s version to v1.24

[ChrsMark]

What does this PR do?

Updates k8s version following #2562 as discussed at https://github.com/elastic/observability-dev/issues/2178. This kind of PRs will be part of the "official" maintenance policy for k8s versions' support handled by @elastic/obs-cloudnative-monitoring

[mergify]

This pull request does not have a backport label. Could you fix it @ChrsMark? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v./d./d./d is the label to automatically backport to the 7./d branch. /d is the digit
  NOTE: backport-skip has been added to this pull request.

[elasticmachine]

💔 Tests Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-06-15T08:06:02.704+0000

• Duration: 74 min 53 sec

Test stats 🧪

Test	Results
Failed	5
Passed	381
Skipped	0
Total	386

Test errors

Expand to view the tests failures

Initializing / End-To-End Tests / fleet_sles15_fleet_mode / Un-enrolling the agent deactivates the agent – Fleet Mode

Expand to view the error details

 Step the agent is un-enrolled 

• no stacktrace

Initializing / End-To-End Tests / fleet_debian_10_arm64_linux_integration / Adding the Linux Integration to an Agent ... – Linux Integration

Expand to view the error details

 Step the agent is listed in Fleet as "online" 

• no stacktrace

Initializing / End-To-End Tests / fleet_ubuntu_22_04_amd64_system_integration / Adding socket_summary system/metrics Integration to a Policy – System Integration

Expand to view the error details

 Step the agent is listed in Fleet as "online" 

• no stacktrace

Initializing / End-To-End Tests / fleet_ubuntu_22_04_amd64_system_integration / Adding filesystem system/metrics Integration to a Policy – System Integration

Expand to view the error details

 Step the agent is listed in Fleet as "online" 

• no stacktrace

Initializing / End-To-End Tests / fleet_debian_10_amd64_system_integration / Adding cpu system/metrics Integration to a Policy – System Integration

Expand to view the error details

 Step the agent is listed in Fleet as "online" 

• no stacktrace

Steps errors

Expand to view the steps failures

Executing ansible-playbook

• Took 13 min 19 sec . View more details here
• Description: /var/lib/jenkins/workspace/2e-tests_e2e-testing-mbp_PR-2644/.venv/bin/ansible-playbook --private-key="/var/lib/jenkins/workspace/2e-tests_e2e-testing-mbp_PR-2644/src/github.com/elastic/e2e-testing/e2essh" --extra-vars="workspace=/var/lib/jenkins/workspace/2e-tests_e2e-testing-mbp_PR-2644/src/github.com/elastic/e2e-testing/ runId=95e903d6 sshPublicKey=/var/lib/jenkins/workspace/2e-tests_e2e-testing-mbp_PR-2644/src/github.com/elastic/e2e-testing/e2essh.pub" --ssh-common-args='-o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null' /var/lib/jenkins/workspace/2e-tests_e2e-testing-mbp_PR-2644/src/github.com/elastic/e2e-testing/.ci/ansible/playbook.yml -i "18.218.214.195," -t setup-stack --extra-vars="buildURL=https://beats-ci.elastic.co/job/e2e-tests/job/e2e-testing-mbp/job/PR-2644/4/ gitSha=e5d10271444e4b0ed40dae9ec359f963987d8c98 build=4 repo=e2e-testing branch=pr-2644 type=ci stackRunner=18.218.214.195 nodeLabel=stack nodeUser=admin nodeImage=ami-0d90bed76900e679a nodeInstanceType=t3.xlarge"

Sleep

• Took 0 min 5 sec . View more details here
• Description: 5

Shell Script

• Took 12 min 54 sec . View more details here
• Description: ssh -tt -o TCPKeepAlive=yes -o ServerAliveInterval=60 -o ServerAliveCountMax=10 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i /var/lib/jenkins/workspace/PR-2644-4-86a76e2a-95ec-43b2-a3fc-fa2b7f9ab0c8/e2essh ec2-user@18.219.104.237 -- 'sudo bash /home/ec2-user/e2e-testing/.ci/scripts/functional-test.sh'

Archive the artifacts

• Took 0 min 0 sec . View more details here
• Description: [2022-06-15T09:04:57.388Z] Archiving artifacts script returned exit code 2

Shell Script

• Took 3 min 21 sec . View more details here
• Description: ssh -tt -o TCPKeepAlive=yes -o ServerAliveInterval=60 -o ServerAliveCountMax=10 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i /var/lib/jenkins/workspace/PR-2644-4-9ae6bfb8-2130-4567-8571-0db1f2021d63/e2essh admin@18.118.208.173 -- 'sudo bash /home/admin/e2e-testing/.ci/scripts/functional-test.sh'

Archive the artifacts

• Took 0 min 0 sec . View more details here
• Description: [2022-06-15T08:57:01.117Z] Archiving artifacts script returned exit code 2

Shell Script

• Took 14 min 24 sec . View more details here
• Description: ssh -tt -o TCPKeepAlive=yes -o ServerAliveInterval=60 -o ServerAliveCountMax=10 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i /var/lib/jenkins/workspace/PR-2644-4-71af6c9f-dd6e-4750-8e24-b0439cb551b8/e2essh admin@13.58.4.208 -- 'sudo bash /home/admin/e2e-testing/.ci/scripts/functional-test.sh'

Archive the artifacts

• Took 0 min 0 sec . View more details here
• Description: [2022-06-15T09:07:25.413Z] Archiving artifacts script returned exit code 2

Shell Script

• Took 17 min 33 sec . View more details here
• Description: ssh -tt -o TCPKeepAlive=yes -o ServerAliveInterval=60 -o ServerAliveCountMax=10 -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i /var/lib/jenkins/workspace/PR-2644-4-37525989-bd39-4b65-9ca7-50d13ed923eb/e2essh ubuntu@18.190.154.194 -- 'sudo bash /home/ubuntu/e2e-testing/.ci/scripts/functional-test.sh'

Archive the artifacts

• Took 0 min 1 sec . View more details here
• Description: [2022-06-15T09:04:52.666Z] Archiving artifacts script returned exit code 2

🐛 Flaky test report

❕ There are test failures but not known flaky tests.

Expand to view the summary

Genuine test errors

💔 There are test failures but not known flaky tests, most likely a genuine test failure.

• Name: Initializing / End-To-End Tests / fleet_sles15_fleet_mode / Un-enrolling the agent deactivates the agent – Fleet Mode
• Name: Initializing / End-To-End Tests / fleet_debian_10_arm64_linux_integration / Adding the Linux Integration to an Agent ... – Linux Integration
• Name: Initializing / End-To-End Tests / fleet_ubuntu_22_04_amd64_system_integration / Adding socket_summary system/metrics Integration to a Policy – System Integration
• Name: Initializing / End-To-End Tests / fleet_ubuntu_22_04_amd64_system_integration / Adding filesystem system/metrics Integration to a Policy – System Integration
• Name: Initializing / End-To-End Tests / fleet_debian_10_amd64_system_integration / Adding cpu system/metrics Integration to a Policy – System Integration

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[ChrsMark]

@mdelapenya shall we upgrade the version of Helm too? It seems that the tests of helm are failing most probably because of versioning?

I would suggest moving to the latest one: https://github.com/helm/helm/releases/tag/v3.9.0

Ah I see those are already updated. I wonder why the failures then 🤔

[mdelapenya]

I think those imports were removed by mistake

[ChrsMark]

My bad 😞 it's my editor that removes those for some reason.

[mdelapenya]

The removed imports are needed, so it seems they were removed by mistake. Could you please re-add them?

[ChrsMark]

@mdelapenya it seems to be ok now, helm and k8s tests passed the failures are on some of the fleet's tests.

[ChrsMark]

Not sure about the backports here. This one should go along with 8.4 I think. @mdelapenya could you please verify the backport labels?