Add Fleet Server and Elastic Agent release notes for 8.19.3 #1848
Conversation
|
A documentation preview will be available soon. Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
| * Correct hints annotations parsing to resolve only `${Kubernetes.*}` placeholders instead of resolving all `${...}` patterns. {agent-pull}9307[#9307] | ||
| * Treat exit code 28 from endpoint binary as non-fatal. {agent-pull}9320[#9320] | ||
| * Fixed jitter backoff strategy reset. {agent-pull}9342[#9342] {agent-issue}8864[#8864] | ||
| * Fix Docker container failing to start with no matching vars: `${Env.elasticsearch_api_key:}` and similar errors by restoring support for `:` to set default values. {agent-pull}9451[#9451] {agent-issue}9328[#9328] |
There was a problem hiding this comment.
| * Fix Docker container failing to start with no matching vars: `${Env.elasticsearch_api_key:}` and similar errors by restoring support for `:` to set default values. {agent-pull}9451[#9451] {agent-issue}9328[#9328] | |
| * Fix Docker container failing to start with `no matching vars: ${Env.elasticsearch_api_key:}` and similar errors by restoring support for `:` to set default values. {agent-pull}9451[#9451] {agent-issue}9328[#9328] |
| * Treat exit code 28 from endpoint binary as non-fatal. {agent-pull}9320[#9320] | ||
| * Fixed jitter backoff strategy reset. {agent-pull}9342[#9342] {agent-issue}8864[#8864] | ||
| * Fix Docker container failing to start with no matching vars: `${Env.elasticsearch_api_key:}` and similar errors by restoring support for `:` to set default values. {agent-pull}9451[#9451] {agent-issue}9328[#9328] | ||
| * Fix deb upgrade by stopping elastic-agent service before stopping endpoint. {agent-pull}9462[#9462] |
There was a problem hiding this comment.
| * Fix deb upgrade by stopping elastic-agent service before stopping endpoint. {agent-pull}9462[#9462] | |
| * Fix deb upgrade by stopping `elastic-agent` service before stopping endpoint. {agent-pull}9462[#9462] |
|
|
||
| Elastic Agent:: | ||
|
|
||
| * On Windows, retry saving the Agent information file to disk. {agent-pull}9224[#9224] {agent-issue}5862[#5862] |
There was a problem hiding this comment.
Should we include the additional description for this issue that was added for the release notes in 9.1.3: https://github.com/elastic/docs-content/pull/2724/files#diff-0476d2b5e8583455aaff701598366cc737043bc8281d1ad393d4790cbbbe6152R45 ?
There was a problem hiding this comment.
This is just based on a difference in how the automation works for Markdown vs. AsciiDoc. I'd rather not manually copy over the description here since all other AsciiDoc release notes only use the summary.
|
|
||
| Elastic Agent:: | ||
|
|
||
| * Upgrade to Go version 1.24.6. {agent-pull}9287[#9287] |
There was a problem hiding this comment.
| * Upgrade to Go version 1.24.6. {agent-pull}9287[#9287] | |
| * Upgrade Go version to 1.24.6. {agent-pull}9287[#9287] |
|
|
||
| Elastic Agent:: | ||
|
|
||
| * Adjust the timeout for Elastic Defend check command. {agent-pull}9560[#9560] {agent-pull}9608[#9608] {agent-pull}9609[#9609] {agent-pull}9546[#9546] {agent-pull}9213[#9213] |
There was a problem hiding this comment.
In the release notes for 9.1.3, it seems Pierre requested that only one of the issues is included for this issue and for the issue on line 58 (maybe the ones that are related to the specific branch, maybe). Not sure if such a change is needed here or not.
|
@colleenmcginnis sorry, I didn’t notice this was set to auto-merge… Should we update the release notes based on the comments, or can we leave it like this? |
2 participants
Adds Fleet Server and Elastic Agent release notes for 8.19.3 from elastic/elastic-agent#9610 and elastic/fleet-server#5357.