-
Notifications
You must be signed in to change notification settings - Fork 709
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
Fix Elastic Agent Fleet Server without TLS e2e tests #6214
Fix Elastic Agent Fleet Server without TLS e2e tests #6214
Conversation
…+ FLEET_SERVER_PORT. Update tests to include new required env vars.
run/e2e-tests match=TestFleetAgentWithoutTLS |
This was failing because of an issue with 8.6 Snapshot version of Elastic Agent |
@naemono as of Elastic Agent v8.6.0 (release version) Fleet Server still binds on Is there any additional option that needs to be set for this to work, like it did until v8.5.x? |
@antoineco we had recent issues with Agent/Fleet e2e tests, and have had them disabled for a bit, and are just re-enabling them with 8.6.1: see #6364 Unfortunately, I can't answer this question quite yet until we re-enable, and begin testing again. From what I'm seeing, there are still issues with forcing localhost: elastic/elastic-agent#2198 |
Running tests manually to test this fix
|
Signed-off-by: Michael Montgomery <mmontg1@gmail.com>
Success @thbkrkr:
|
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.
LGTM
Do we need to document that Fleet >= 8.6.1 without TLS works only from ECK 2.7.0?
Decided to do nothing, as we still have fleet/agent e2e tests disabled due to #6331 |
Elastic Agent Fleet Server e2e tests without TLS continue to fail with Agents failing to connect to Fleet Server with:
It seems as though Elastic Agent Fleet Server is binding to
localhost:8220
from logs:This would prevent communication from anything outside of the pod's containers themselves, and would certainly stop other pods from communicating with this port via a service.
This change uses the environment variables defined in the Agent Fleet Documentation to instruct Elastic Agent Fleet Server to listen on
0.0.0.0:8220
instead, and should resolve the communication issues in the e2e tests.E2E tests passed when running locally with this change.
Will run e2e tests suite in this PR and see how it goes.
--edit--
closes #6367