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.

Sign up for GitHub

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

Jump to bottom

[Elastic Agent] Updating policy with updated Kibana should ensure communication is possible before updating the fleet configuration #24485

Closed
blakerouse opened this issue Mar 10, 2021 · 0 comments · Fixed by #24489
Closed

[Elastic Agent] Updating policy with updated Kibana should ensure communication is possible before updating the fleet configuration #24485

blakerouse opened this issue Mar 10, 2021 · 0 comments · Fixed by #24489
Assignees
@blakerouse
Labels
Team:Elastic-Agent Label for the Agent team

Comments

@blakerouse
Copy link
Contributor

At the moment Elastic Agent updates its fleet.yml with the Kibana connection information from the policy. Elastic Agent currently doesn't verify that it can actually communicate with the new connection information before setting that as the new client and writing it to the fleet.yml.

If Elastic Agent cannot communicate back to Kibana with that information, then the policy should fail and should not be ACK'd.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@blakerouse blakerouse

Labels
Team:Elastic-Agent Label for the Agent team
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Elastic Agent] Add verification check when updating communication to Kibana. blakerouse/beats
1 participant
@blakerouse