[8.x](backport #4574) Add DRA FIPS artifacts to package pipeline #4681
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
Add FIPS="true" env flag to packageing pipeline. Packaging pipline uses microsoft/go instead of golang/go to build DRA artifacts for FIPS. Change package name from fleet-server-*-fips to fleet-server-fips-*. (cherry picked from commit 8bb8c74)
github-actions
bot
added
Team:Elastic-Agent-Control-Plane
michel-laterman
approved these changes
Mar 25, 2025
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the problem this PR solves?
Provide FIPS dra artifacts.
How does this PR solve the problem?
Add
FIPS="true"env flag to packageing pipeline.Packaging pipline uses microsoft/go instead of golang/go to build DRA artifacts for FIPS.
Change package name from
fleet-server-*-fipstofleet-server-fips-*.Design Checklist
I have ensured my design is stateless and will work when multiple fleet-server instances are behind a load balancer.I have or intend to scale test my changes, ensuring it will work reliably with 100K+ agents connected.I have included fail safe mechanisms to limit the load on fleet-server: rate limiting, circuit breakers, caching, load shedding, etc.Checklist
I 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 toolRelated issues
This is an automatic backport of pull request #4574 done by [Mergify](https://mergify.com).