Add Pipeline to deploy custom agent image for FIPS testing#8035
Add Pipeline to deploy custom agent image for FIPS testing#8035michel-laterman merged 60 commits intoelastic:mainfrom
Conversation
|
buildkite test this |
|
@v1v @pazone, can you take a look at this, we need permissions in order to push a custom image to use in the CFT region |
Can you share the URL link to the error? I'm not familiar with the current user and namespace, but as far as I see, those details are stored at https://github.com/elastic/elastic-agent/blob/aa224536eadf49f8b9b962df240c0caa4861970e/.buildkite/hooks/pre-command#l17.
I see you have enabled the |
Updatecli tests$ gh pr checkout 8035
$ git checkout -b test/fips-ech-updatecli
$ git push origin test/fips-ech-updatecli
$ # modify .ci/updatecli/values.d/scm.yml to use my fork
$ GITHUB_TOKEN=$(gh auth token) \
GITHUB_ACTOR=v1v \
BRANCH_NAME=test/fips-ech-updatecli updatecli apply \
--config .ci/updatecli/updatecli-bump-vm-images.yml \
--values .ci/updatecli/values.d/scm.ymldiff --git a/.ci/updatecli/values.d/scm.yml b/.ci/updatecli/values.d/scm.yml
index 2708262728..c01cb89d50 100644
--- a/.ci/updatecli/values.d/scm.yml
+++ b/.ci/updatecli/values.d/scm.yml
@@ -1,8 +1,8 @@
scm:
enabled: true
- owner: elastic
+ owner: v1vProduced v1v#9 |
v1v
left a comment
There was a problem hiding this comment.
LGTM, the questions I asked earlier are not blockers, but likely something to be done in follow-up
v1v
left a comment
There was a problem hiding this comment.
LGTM, the questions I asked earlier are not blockers, but likely something to be done in follow-up
💛 Build succeeded, but was flaky
Failed CI StepsHistory
|
|
Add a new buildkite pipeline to build a custom agent image and use it in an ECH deployment for testing. Run FIPS integration tests on VMs with a FIPS provider. (cherry picked from commit 5908ed2) # Conflicts: # testing/integration/fleetserver_fips_test.go
Add a new buildkite pipeline to build a custom agent image and use it in an ECH deployment for testing. Run FIPS integration tests on VMs with a FIPS provider. (cherry picked from commit 5908ed2)
… FIPS testing (#8415) * Add Pipeline to deploy custom agent image for FIPS testing (#8035) Add a new buildkite pipeline to build a custom agent image and use it in an ECH deployment for testing. Run FIPS integration tests on VMs with a FIPS provider. (cherry picked from commit 5908ed2) * Fix pre-command to support extended testing (#8418) (cherry picked from commit 97246c1) --------- Co-authored-by: Michel Laterman <82832767+michel-laterman@users.noreply.github.com>
…ts-oblt-cli * feature/serverless-its-oblt-cli: (51 commits) as agreed let's move the group to the kb.integration pipeline Update .github/workflows/serverless-project.yml ci: invoke serverless integration tests package from BK github-actions: create a serverless project daily [tests] split up serverless and resource leaks integration tests (#8396) chore: Update to elastic/beats@dfdc12e33de0 (#8446) Lock upgrade marker (#8254) build(deps): bump github.com/elastic/elastic-agent-system-metrics from 0.11.12 to 0.11.13 (#8420) Add docker image name template and renamed fips cloud specs (#8429) buildkite(scripts): refactor common scripts (#8365) Use require.Eventually to try and address flakiness (#8421) Fix pre-command to support extended testing (#8418) [Automation] Bump Golang version to 1.24.4 (#8384) chore: Update to elastic/beats@aed2a8b768bd (#8423) [main][Automation] Update versions (#8425) Add Pipeline to deploy custom agent image for FIPS testing (#8035) ci: automatically update OTel components (#8288) [Automation] Bump VM Image version to 1749258065 (#8390) fix: increase context timeout to accommodate for slower machines in Test_checkForUnprivilegedVault (#8374) otel: add cumulativetodeltaprocessor to EDOT collector (#8372) ...





What does this PR do?
Add a new buildkite pipeline to build a custom agent image and use it in an ECH deployment for testing.
Why is it important?
FIPS integration tests will require a custom agent running in the CFT region.
Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration filesI have added tests that prove my fix is effective or that my feature worksI have added an entry in./changelog/fragmentsusing the changelog toolDisruptive User Impact
N/A