-
Notifications
You must be signed in to change notification settings - Fork 168
Adding test for enrolling local FIPS agent into ECH FIPS Fleet Server #8197
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
base: main
Are you sure you want to change the base?
Adding test for enrolling local FIPS agent into ECH FIPS Fleet Server #8197
Conversation
This pull request does not have a backport label. Could you fix it @ycombinator? 🙏
|
|
💔 Build Failed
Failed CI Steps
History
cc @ycombinator |
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
ctx, cancel := context.WithTimeout(context.Background(), 3*time.Minute) | ||
defer cancel() | ||
|
||
policyResp, _, err := tools.InstallAgentWithPolicy(ctx, t, installOpts, fixture, info.KibanaClient, basePolicy) |
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.
Where is the part that defines this enrollment to happen to the Fleet Server as part of the Integrations Server on ECH? I checked the code and understand it is enrolling to the default Fleet Server, but I don't easily spot where the connection to Integrations Server is made.
What does this PR do?
This PR adds an integration test that a) enrolls a locally-built FIPS-capable Elastic Agent into a FIPS-capable Fleet Server running in ECH, b) adds the
system
integration to that Agent's policy, and c) ensures that data from thesystem
integration shows up in Elasticsearch.Why is it important?
This test proves that it's possible for a local (on-prem) FIPS-capable Elastic Agent to enroll into a FIPS-capable Fleet Server (aka Integrations Server) running in EC; while also exercising the connection between Fleet and the Elastic Package Registry (EPR) by installing the
system
integration; and also ensuring that the data path from Agent to Elasticsearch works as well.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/fragments
using the changelog toolDisruptive User Impact
None; this PR adds an integration test.