-
Notifications
You must be signed in to change notification settings - Fork 117
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
Comments
Comment on the older stacks: 7.11 and 7.12 are not expected to work. |
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). |
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). |
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 . |
Status update: It looks like we fixed all issues or at least they're not bumping up here. |
@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 ❤️ |
The goal of this issue is to ensure that the Fleet Server is enabled for the Elastic stack setup.
Known differences / to be solved:
- [ ] Blocker: Elastic-Agent: failed: could not decode the response, raw response: no matching action beats#24467(most likely not a blocker anymore, but no-go for support of 7.12 and 7.11, environment variables are in conflict between versions)Are older stacks working?
- [ ] 7.12.0no: elastic/beats#24467 (comment)- [ ] 7.11.2no: elastic/beats#24467 (comment)The text was updated successfully, but these errors were encountered: