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

Validate Elastic Agent compatibility #238

Closed
ruflin opened this issue Mar 24, 2021 · 1 comment · Fixed by #239
Closed

Validate Elastic Agent compatibility #238

ruflin opened this issue Mar 24, 2021 · 1 comment · Fixed by #239
Assignees

Comments

@ruflin
Copy link
Member

ruflin commented Mar 24, 2021

Currently Elastic Agent talks to Kibana and verifies the version. In the future this will fleet-server. For Elastic Agent there are 2 compatibility parts:

  • Standalone: Compatibility with Elasticsearch
  • Managed: Compatibility with fleet-server

As the compatibility with Elasticsearch in the managed mode is enforced by fleet-server (#167) this should not be an issue. In general the compatibility looks as following:

Elastic Agent <= fleet-server <= Elasticsearch

The bugfix release might differ. The last minor or Elastic Agent in a major should be compatible with the first minor of the next major of fleet-server. Same for Elasticsearch. This means fleet-server / Elasticsearch must be upgraded first.

@elasticmachine
Copy link
Contributor

Pinging @elastic/agent (Team:Agent)

@blakerouse blakerouse self-assigned this Mar 24, 2021
@blakerouse blakerouse transferred this issue from elastic/beats Apr 14, 2021
@blakerouse blakerouse changed the title Validate fleet-server compatibility in Elastic Agent Validate Elastic Agent compatibility Apr 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants