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

Elastic stack: support Fleet Server #278

Closed
6 of 7 tasks
mtojek opened this issue Mar 8, 2021 · 6 comments · Fixed by elastic/integrations#889
Closed
6 of 7 tasks

Elastic stack: support Fleet Server #278

mtojek opened this issue Mar 8, 2021 · 6 comments · Fixed by elastic/integrations#889
Assignees

Comments

@mtojek
Copy link
Contributor

mtojek commented Mar 8, 2021

The goal of this issue is to ensure that the Fleet Server is enabled for the Elastic stack setup.

Known differences / to be solved:

Are older stacks working?
- [ ] 7.12.0 no: elastic/beats#24467 (comment)
- [ ] 7.11.2 no: elastic/beats#24467 (comment)

@ruflin
Copy link
Contributor

ruflin commented Mar 16, 2021

Comment on the older stacks: 7.11 and 7.12 are not expected to work.

@mtojek
Copy link
Contributor Author

mtojek commented Mar 16, 2021

It depends on the set of environment variables. Maybe it's possible to select such set that all stacks work correctly. Even though I agree to give priority to the latest (7.13).

@mtojek
Copy link
Contributor Author

mtojek commented Mar 16, 2021

Status update:

With support of @nchaulet , I managed to start the agent, connect to the fleet server and enroll. I suppose we eliminated this way one blocker. Unfortunately it seems that we can't comprise a complete list of environment vars that will be suitable for 7.13, 7.12, 7.11 as vars are in conflict with each other (different behavior).

@mtojek
Copy link
Contributor Author

mtojek commented Mar 23, 2021

Next status update:

Another issue spotted. Either the agent can't pick up the policy or it doesn't confirm that it was picked - elastic/kibana#95179 .

@mtojek
Copy link
Contributor Author

mtojek commented Apr 6, 2021

Status update:

It looks like we fixed all issues or at least they're not bumping up here.

@ruflin
Copy link
Contributor

ruflin commented Apr 6, 2021

@mtojek Thanks a lot for pushing through all these. It caused a lot of work on your end but helped the other teams to make the product better ❤️

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.

2 participants