-
Notifications
You must be signed in to change notification settings - Fork 41
chore: run k8s and helm test suites on ARM #1471
Conversation
💔 Tests Failed
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪Test errors
Expand to view the tests failures> Show only the first 10 test failures
|
| Test | Results |
|---|---|
| Failed | 15 |
| Passed | 232 |
| Skipped | 0 |
| Total | 247 |
Genuine test errors 
💔 There are test failures but not known flaky tests, most likely a genuine test failure.
- Name:
Initializing / End-To-End Tests / ubuntu-18.04_helm_apm-server / The APM Server chart will create recommended K8S resources – APM Server - Name:
Initializing / End-To-End Tests / arm64_helm_apm-server / The APM Server chart will create recommended K8S resources – APM Server - Name:
Initializing / End-To-End Tests / arm64_kubernetes-autodiscover_kubernetes-autodiscover && filebeat / Logs collection from running pod – Filebeat - Name:
Initializing / End-To-End Tests / arm64_kubernetes-autodiscover_kubernetes-autodiscover && filebeat / Logs collection from failing pod – Filebeat - Name:
Initializing / End-To-End Tests / arm64_kubernetes-autodiscover_kubernetes-autodiscover && filebeat / Logs collection from short-living cronjobs – Filebeat - Name:
Initializing / End-To-End Tests / arm64_kubernetes-autodiscover_kubernetes-autodiscover && filebeat / Logs collection from a pod with an init container – Filebeat - Name:
Initializing / End-To-End Tests / arm64_kubernetes-autodiscover_kubernetes-autodiscover && filebeat / Logs collection from a pod with an ephemeral container – Filebeat - Name:
Initializing / End-To-End Tests / arm64_kubernetes-autodiscover_kubernetes-autodiscover && filebeat / Logs collection from running pod and metadata enrichment using add_kubernetes_metadata – Filebeat - Name:
Initializing / End-To-End Tests / arm64_kubernetes-autodiscover_kubernetes-autodiscover && filebeat / Enrichment of normal input using add_kubernetes_metadata – Filebeat - Name:
Initializing / End-To-End Tests / arm64_kubernetes-autodiscover_kubernetes-autodiscover && heartbeat / Monitor pod availability using hints with named ports – Heartbeat - Name:
Initializing / End-To-End Tests / arm64_kubernetes-autodiscover_kubernetes-autodiscover && heartbeat / Monitor service availability using hints – Heartbeat - Name:
Initializing / End-To-End Tests / arm64_kubernetes-autodiscover_kubernetes-autodiscover && heartbeat / Monitor service unavailability using hints – Heartbeat - Name:
Initializing / End-To-End Tests / arm64_kubernetes-autodiscover_kubernetes-autodiscover && heartbeat / Monitor nodes using hints – Heartbeat - Name:
Initializing / End-To-End Tests / arm64_kubernetes-autodiscover_kubernetes-autodiscover && metricbeat / Metrics collection stops when the pod is stopped – Metricbeat - Name:
Initializing / End-To-End Tests / arm64_kubernetes-autodiscover_kubernetes-autodiscover && metricbeat / Metrics collection configured with hints with named ports – Metricbeat
jsoriano
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM if it looks good to jenkins 👍
|
@jmlrt we are bumping kind and k8s versions in this PR, and we see that APM Server helm chart fails consistently: https://beats-ci.elastic.co/blue/organizations/jenkins/e2e-tests%2Fe2e-testing-mbp/detail/PR-1471/6/tests
Are helm charts supporting k8s 1.21.1? |
Not sure, I didn't tested them yet with 1.21. Is it also failing for filebeat and metricbeat charts or only apm-server? |
|
Only for APM Server, the other two pass as expected |
|
@mdelapenya, I did some tests with apm-server 7.14.0 on GKE v1.21.3-gke.1100 which were successful. However, I never tested these charts with ARM64 so I don't know if they are compatible. Do you have a bit more details about what is failing? |
|
This pull request does not have a backport label. Could you fix it @mdelapenya? 🙏
|
Upss I think I missed your comment. Sorry about that 😞 Will take a look ASAP |
|
With the merging of #1740 I did attempt to get docker daemon running inside the arm VM's. Apparently, it is not as straightforward as amd64, but if we could get that working we can quickly expand our test matrix to include support for these suites on arm almost instantly. This is all assuming that docker images, kind, k8s all play nicely together in a pure ARM environment. |
|
This pull request is now in conflict. Could you fix it @mdelapenya? 🙏 |
|
Closing as outdated |
What does this PR do?
It bumps the k8s and Kind versions to a version that supports ARM. For kind, it appeared in v0.11.0, which according to its changelog requires a 1.21.1 version of k8s.
Why is it important?
We want to verify those test suites on ARM
Checklist
make unit-test), and they are passing locallymake noticein the proper directory)Author's Checklist