ci: configure kind/k8s for k8s in metricbeat only#30747
Conversation
|
This pull request does not have a backport label. Could you fix it @v1v? 🙏
NOTE: |
ChrsMark
left a comment
There was a problem hiding this comment.
lgtm, thank you for fixing this!
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
|
@v1v I think we can merge this one? |
(cherry picked from commit 3560733) # Conflicts: # Jenkinsfile
(cherry picked from commit 3560733) # Conflicts: # Jenkinsfile
(cherry picked from commit 3560733) # Conflicts: # Jenkinsfile
What does this PR do?
Add support for installing
kind/k8sonly if running the metricbeat goIngTest stage.NOTE:
kind/k8sis only needed when testing the k8s module, so it might be installed for other modules, but this is the approach we can without much complexity in the CI.Why is it important?
The k8s module is tested in two places:
beats/deploy/kubernetes/Jenkinsfile.yml
Lines 20 to 22 in 9e6536d
beats/Jenkinsfile
Line 323 in 9e6536d
beats/metricbeat/Jenkinsfile.yml
Lines 27 to 30 in 9e6536d
Only
1is in charge to install the given Kind and K8s versions. but2requires those tools. Those tools are installed in the CI workers as part of the default installed toolchain (kind versionv0.7.0and k8s versionv0.12.0.This proposal is trying to leverage the IntTests for
metricbeatby installing the k8s/kind when needed, unfortunately we cannot do only when the module is not k8s, unless the build system in metricbeat is in charge of preparing the environment.Related issues