This section summarizes the changes in each release.
Also see:
-
{kibana-ref}/release-notes.html[{kib} release notes]
-
{beats-ref}/release-notes.html[{beats} release notes]
Review important information about the {fleet} and {agent} 8.5.2 release.
- {fleet}
- {fleet-server}
- {agent}
-
-
No bug fixes in this release
-
Review important information about the {fleet} and {agent} 8.5.1 release.
Unable to add {fleet-server} integration on Windows
Details
We discovered a high severity issue in version 8.5.1 that only affects Windows users in self-managed environments. When you attempt to add a {fleet-server}, {kib} is unable to add the {fleet-server} integration, and the {fleet-server} polices are created without the necessary integration. For more information, see issue #144880.
Impact
This issue will be resolved in version 8.5.2. We advise Windows users not to upgrade to version 8.5.1.
Offline {agent}s fail to unenroll after timeout has expired
Details
A known issue in {fleet-server} 8.5.1 prevents offline agents from being automatically unenrolled after the unenrollment timeout expires.
Impact
Offline agents will be displayed in the {fleet} Agents list until you explicitly force unenroll them. You can do this through the {fleet} UI or by using the API.
To use the API:
-
Find agent’s ID. Go to {fleet} > Agents and click the agent to see its details. Copy the Agent ID.
-
In a terminal window, run:
curl -u <username>:<password> --request POST \ --url <kibana_url>/api/fleet/agents/<agentID>/unenroll \ --header 'content-type: application/json' \ --header 'kbn-xsrf: xx' \ --data-raw '{"force":true,"revoke":true}' \ --compressed
Where
<agentID>
is the ID you copied in the previous step.
- {agent}
-
-
Improve shutdown logs #1618
-
- {fleet}
-
-
Make asset tags space aware #144066
-
- {fleet-server}
-
-
No bug fixes for this release
-
- {agent}
Review important information about the {fleet} and {agent} 8.5.0 release.
Breaking changes can prevent your application from optimal operation and performance. Before you upgrade, review the breaking changes, then mitigate the impact to your application.
{fleet-server} and {agent} now reject certificates signed with SHA-1
Details
With the upgrade to Go 1.18, {fleet-server} now rejects certificates signed with
SHA-1. For more information, refer to the Go 1.18
release notes.
Impact
Do not sign certificates with SHA-1. If you are using old certificates signed
with SHA-1, update them now.
The 8.5.0 release adds the following new and notable features.
- {fleet}
- {fleet-server}
- {agent}
- {fleet}
- {agent}
- {fleet}
- {fleet-server}
-
-
Fix a race condition between the unenroller goroutine and the main goroutine for the coordinator monitor #1738
-
Remove events from agent check-in body #1774
-
Improve authc debug logging #1870
-
Add error detail to catch-all HTTP error response #1854
-
Fix issue where errors were ignored when written to {es} #1896
-
Update
apikey.cache_hit
log field name to match convention #1900 -
Custom server limits are no longer ignored when default limits are loaded #1841 #1912
-
Use separate rate limiters for internal and external API listeners to prevent {fleet-server} from shutting down under load #1859 #1904
-
Fix
fleet.migration.total
log key overlap #1951
-
- {agent}
-
-
Fix a panic caused by a race condition when installing the {agent} #806 #823
-
Use the {agent} configuration directory as the root of the
inputs.d
folder #663 #840 -
Fix unintended reset of source URI when downloading components #1252
-
Create separate status reporter for local-only events so that degraded {fleet} check-ins no longer affect health of successful {fleet} check-ins #1157 #1285
-
Add success log message after previous check-in failures #1327
-
Fix docker provider
add_fields
processors #1420 -
Fix admin permission check on localized windows #1552
-