Skip to content
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

Backport elastic-agent#1867 #38785

Conversation

michel-laterman
Copy link
Contributor

@michel-laterman michel-laterman commented Apr 9, 2024

Proposed commit message

Backport elastic/elastic-agent#1867 that forces the agent use use certificate verification instead of full verification when connecting to a local fleet-server instance.

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

@michel-laterman michel-laterman added bug backport Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team labels Apr 9, 2024
@botelastic botelastic bot added needs_team Indicates that the issue/PR needs a Team:* label and removed needs_team Indicates that the issue/PR needs a Team:* label labels Apr 9, 2024
@michel-laterman michel-laterman force-pushed the backport-elasticagent-localhost-fix branch from a650f1c to 721f13d Compare April 9, 2024 15:54
@elasticmachine
Copy link
Collaborator

elasticmachine commented Apr 9, 2024

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Duration: 52 min 51 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

Backport elastic-agent#1867 that forces the agent use use certificate
verification instead of full verification when connecting to a local
fleet-server instance. This change should resolve fleet-server#3435
which is a change in how certificates are verified when the beats lib in
7.17 is updated in fleet-server.
Also fix linter issues
@michel-laterman
Copy link
Contributor Author

Closing this, I don't know if we need the backport.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport bug Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants