-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
validate kubernetes templates in .CI #417
Conversation
This pull request does not have a backport label. Could you fix it @narph? 🙏
NOTE: |
🌐 Coverage report
|
/test |
.ci/Jenkinsfile
Outdated
@@ -61,6 +61,7 @@ pipeline { | |||
dir("${BASE_DIR}"){ | |||
setEnvVar('BEAT_VERSION', sh(label: 'Get beat version', script: 'make get-version', returnStdout: true)?.trim()) | |||
log(level: 'INFO', text: "env.BEAT_VERSION=${env.BEAT_VERSION}") | |||
cmd(label: 'check', script: 'make -C deploy/kubernetes all') |
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.
I'd say to move this to the k8s specific stage, see L153
, the k8s stage runs only if there are changes matching the regex (^deploy/kubernetes/.*|^version/docs/version.asciidoc)
(see L54) on a PR basis or by default on branches
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.
OTOH, what's the difference between make -C deploy/kubernetes all
and make -C deploy/kubernetes test
, since test
is already in place.
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.
make -C deploy/kubernetes all
generates the kube*.yml files after which a MAKE check-no-changes
should be ran to make sure the templates are up to date. This step should take place in the Check area
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.
What do you think if:
make -C deploy/kubernetes all
could be renamed to a different make goal, so the name of the goal reflects what it does.- change
make check-ci
to run the above make goal.
Lines 44 to 48 in 63b682f
.PHONY: check-ci | |
check-ci: | |
@mage update | |
@$(MAKE) notice | |
@$(MAKE) check-no-changes |
With the above, there is no need to change the pipeline, there is only one make goal to run the checks either locally or in the CI, and additionally the make goal all
could reflect what it does
What do you think?
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.
I have no issues with that option as well, made the necessary changes
This pull request does not have a backport label. Could you fix it @narph? 🙏
NOTE: |
What's the reason the changes in the CI and Makefile are not backported to |
we could, we just need to update the version to 8.2 |
* update version * test valiadtion * invalid * invalid * valid * move func * move func (cherry picked from commit 23238de) # Conflicts: # version/docs/version.asciidoc
* validate kubernetes templates in .CI (#417) * update version * test valiadtion * invalid * invalid * valid * move func * move func (cherry picked from commit 23238de) # Conflicts: # version/docs/version.asciidoc * update version Co-authored-by: Mariana Dima <[email protected]>
…use-orka * 'main' of github.com:elastic/elastic-agent: (23 commits) [Automation] Update go release version to 1.17.10 (elastic#432) [Automation] Update elastic stack version to 8.3.0-4149272f for testing (elastic#435) [Automation] Update elastic stack version to 8.3.0-19aba912 for testing (elastic#430) Add extra k8s resources in clusterRole (elastic#424) [Automation] Update elastic stack version to 8.3.0-8ee1196f for testing (elastic#422) [Automation] Update elastic stack version to 8.3.0-53513548 for testing (elastic#421) Add tags option during enroll/install (elastic#336) validate kubernetes templates in .CI (elastic#417) add missing kube-api resources from managed agent manifest (elastic#381) Create snyk-scan.yml (elastic#397) [Automation] Update elastic stack version to 8.3.0-d380914f for testing (elastic#414) [Automation] Update elastic stack version to 8.3.0-5c1ff35f for testing (elastic#413) [Automation] Update elastic stack version to 8.3.0-6ba9f710 for testing (elastic#410) [Automation] Update elastic stack version to 8.3.0-a1c5cfff for testing (elastic#406) [Automation] Update elastic stack version to 8.3.0-7f585873 for testing (elastic#401) [Automation] Update elastic stack version to 8.3.0-0b6ea9f2 for testing (elastic#399) ci: enable coverage (elastic#377) Remove last dependencies on beats repo (elastic#387) Remove dependency on libbeat (elastic#344) [Automation] Update elastic stack version to 8.3.0-cb2ce38c for testing (elastic#383) ...
What does this PR do?
Adds validation of kube templates in CI
Why is it important?
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.