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.

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

Add restrictions to agent upgrade docs #971

Merged
merged 2 commits into from
Mar 13, 2024

Conversation

kilfoyle
Copy link
Contributor

@kilfoyle kilfoyle commented Mar 12, 2024

This updates the Upgrade Fleet-managed Elastic Agents page with a few restrictions about when upgrades are eligible.

@criamico Please let me know if if I've missed anything.

Closes: #966

screen

@kilfoyle kilfoyle requested a review from a team as a code owner March 12, 2024 16:32
Copy link

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

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.

@kilfoyle kilfoyle requested a review from criamico March 12, 2024 16:33
@kilfoyle
Copy link
Contributor Author

@elasticmachine run docs-build rebuild

@kilfoyle
Copy link
Contributor Author

@elasticmachine merge upstream

* To be upgradeable, {agent} must not be running inside a container.
* To be upgradeable in a Linux environment, {agent} must be running as a service. The Linux Tar install instructions for {agent} provided in {fleet} include the commands to run it as a service. {agent} RPM and DEB system packages cannot be upgraded through {fleet}.

These restrictions apply whether you are upgrading {agents} individually or in bulk. In the event that an upgrade isn't elligible, {fleet} generates a warning message when you attempt the upgrade.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo: elligible instead of eligible

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oops! It seems I can't spell. :-)
This is fixed in fff169f

@criamico
Copy link
Contributor

Thanks for the quick PR @kilfoyle!

@kilfoyle kilfoyle requested a review from criamico March 13, 2024 10:09
Copy link
Contributor

@criamico criamico left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🚀

@kilfoyle
Copy link
Contributor Author

@elasticmachine run docs-build

Copy link
Contributor

@karenzone karenzone left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@kilfoyle kilfoyle merged commit 7cf7c2d into elastic:main Mar 13, 2024
3 checks passed
mergify bot pushed a commit that referenced this pull request May 3, 2024
* Add restrictions to agent upgrade docs

* Fix spelling of 'eligible'

(cherry picked from commit 7cf7c2d)
kilfoyle added a commit that referenced this pull request May 3, 2024
* Add restrictions to agent upgrade docs

* Fix spelling of 'eligible'

(cherry picked from commit 7cf7c2d)

Co-authored-by: David Kilfoyle <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[REQUEST]: Fleet - Improve agent upgrade docs
3 participants