-
Notifications
You must be signed in to change notification settings - Fork 83
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
[7.16] Support multiple endpoints #965
[7.16] Support multiple endpoints #965
Conversation
(cherry picked from commit 50affd5)
* Add communication to Elastic Agent. * Fix command-line args and config from Agent. * Fix tests. * Handle config errors on initial config from Agent. * Log to err on failure. * Add syncing of the log writter. * Add docstring. * Re-structure the log init. * Remove unused code in logger. * Fix logging of failed start. * Don't become a leader until fleet.agent.id is set. * Fixes from code review. (cherry picked from commit d40570d)
Cherry pick/master to 7.x
…lastic#79) (cherry picked from commit 376dedd)
This commit is adding execution permission to dependencies-report script which are required during the unified release build. (cherry picked from commit 19fd842) Co-authored-by: Julien Mailleret <[email protected]>
[Backport 7.x]: Reduce actions fetching interval if the full page of action documents was fetched
…sults-backport [Backport 7.x] Flatten .fleet-actions-results schema
* Add ssl configuration to fleet server http configuration. * Add log message when tls disabled. * Fix import. * Fix integration test. (cherry picked from commit 9d451b7)
Upgrade to Go 1.15
* Moved it to testing/esutil package because it is still used for integration testing indices bootstrapping
* Remove saved objects code * Make check happy
The index monitoring got broken dues to replacing the original .fleet-actions and .fleet-policies indices with aliases. This change uses the first index global checkpoint value received from stats and returns the error if there are more than two indices for alias for any reason.
(cherry picked from commit 0069815)
* Add API key invalidation on unenroll ACK. * Fix import location. * Fix test. (cherry picked from commit dc762b5)
…elastic#122) * Add optional maximum connection limit to the server. No more than N connections will be active at any time. * And licenses * And notice
* Add /api/status endpoint. * Run fmt. * Remove version from status. (cherry picked from commit 7cb2930)
…ing (elastic#830) Co-authored-by: apmmachine <[email protected]>
…ing (elastic#835) Co-authored-by: apmmachine <[email protected]>
…ing (elastic#840) Co-authored-by: apmmachine <[email protected]>
…ing (elastic#851) Co-authored-by: apmmachine <[email protected]>
(cherry picked from commit 8a4855b) Co-authored-by: Sean Cunningham <[email protected]>
This was coming out of the debugging session around fleet-server where some of the log messages were not too clear to me on what these mean.
…ing (elastic#866) Co-authored-by: apmmachine <[email protected]>
…ing (elastic#871) Co-authored-by: apmmachine <[email protected]>
…ing (elastic#885) Co-authored-by: apmmachine <[email protected]>
…ing (elastic#892) Co-authored-by: apmmachine <[email protected]>
…ing (elastic#900) Co-authored-by: apmmachine <[email protected]>
…ing (elastic#912) Co-authored-by: apmmachine <[email protected]>
…ing (elastic#917) Co-authored-by: apmmachine <[email protected]>
…ing (elastic#922) Co-authored-by: apmmachine <[email protected]>
…ing (elastic#928) Co-authored-by: apmmachine <[email protected]>
…ing (elastic#932) Co-authored-by: apmmachine <[email protected]>
…#937) * keep trucking on ES availability errors; more tests to come (cherry picked from commit 7fb0138) * don't attempt to distinguish between errors, just keep retrying (cherry picked from commit 2c75552) * move error blackholing up the stack so the monitor will never crash, added additional logging (cherry picked from commit f5fead9) * pr feedback (cherry picked from commit 1886dc5) * upped logging level, properly wrapped errors (cherry picked from commit 97524dc) Co-authored-by: bryan <[email protected]>
…ing (elastic#941) Co-authored-by: apmmachine <[email protected]>
…ing (elastic#947) Co-authored-by: apmmachine <[email protected]>
…ing (elastic#950) Co-authored-by: apmmachine <[email protected]>
…ing (elastic#956) Co-authored-by: apmmachine <[email protected]>
…ing (elastic#961) Co-authored-by: apmmachine <[email protected]>
This pull request is now in conflicts. Could you fix it @michalpristas? 🙏
|
This pull request does not have a backport label. Could you fix it @michalpristas? 🙏
NOTE: |
What is the problem this PR solves?
What this PR solves is a problem when agent got unenrolled on heavier load when agent managing fleet server cannot checkin to it's own server so it will fallback to unenroll.
Closes #741
How does this PR solve the problem?
Problem is solved by adding internal endpoint which is used for communication on local network (with agent handling fleet server)
It lets FS to spin up 2 set of handlers, one on public 8220 and one on port defined in config.
How to test this PR locally
This needs to be tested with work on
elastic-agent
Link: elastic/beats#28993Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.