-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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 Agent] Adjust to Fleet Server connection information from Kibana in configuration #24713
Conversation
Pinging @elastic/agent (Team:Agent) |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
This is now ready to land. The change has already landed in Kibana and Endpoint Security. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this seems rather mechanical code change. looks good i will test it locally before approving
} | ||
} | ||
|
||
return nil | ||
return newAST.root.(*Dict), nil |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this can panic
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added a guard to prevent possible panic
} | ||
values[idx] = newAST.root | ||
} | ||
} | ||
return nil | ||
return l, nil |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
returning same what we passed in?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is so mapList
and mapDict
have the same behavior of returning possible a new node. In the case of mapList
it will not return a new node, but in mapDict
it does.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
…bana in configuration (#24713) (#24992) * Adjust fleet.kibana.* to just fleet.* * Switch from fleet.kibana.* to fleet.* for connection. * Add changelog entry. * Add check to ensure no possible panic in mapDict. (cherry picked from commit 974f255) Co-authored-by: Blake Rouse <[email protected]>
What does this PR do?
This adjusts the Elastic Agent to look for connection information to Fleet Server at
fleet.hosts
instead offleet.kibana.hosts
.NOTE: This is a breaking change and needs to land at the same time as elastic/kibana#94364
NOTE: This also requires that Endpoint Security adjust how it reads the Fleet configuration from the configuration that Elastic Agent sends it.
Why is it important?
With the transition to Fleet Server from Kibana, Elastic Agent no longer talks directly to Kibana and needs connection information to Fleet Server instead of Kibana.
Checklist
[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration filesCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.