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

[8.x] Add steps to configure a PGP key for agent upgrade (backport #984) #1655

Merged
merged 1 commit into from
Jan 29, 2025

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Jan 29, 2025

This adds instructions for air-gapped environments on how to set server.pgp.upstream_url so that Elastic Agents can access the PGP/GPG key required for upgrade.

See docs preview page.

Please let me know if I've missed anything, especially in the "Note that" section under the steps.

Closes: #980
Rel: https://github.com/elastic/sdh-beats/issues/4496


This is an automatic backport of pull request #984 done by Mergify.

* Add steps to configure a PGP key for agent upgrade

* Rebuild

* Add alternative of using fleet-server endpoint

* fixup

* Update logic based on Michel's input

* Add Luca's suggestions

* Update docs/en/ingest-management/fleet/air-gapped.asciidoc

Co-authored-by: Luca Belluccini <luca.belluccini@elastic.co>

* Update docs/en/ingest-management/fleet/air-gapped.asciidoc

* Update docs/en/ingest-management/fleet/air-gapped.asciidoc

* Update docs/en/ingest-management/fleet/air-gapped.asciidoc

---------

Co-authored-by: Luca Belluccini <luca.belluccini@elastic.co>
(cherry picked from commit 4429a6e)
@mergify mergify bot added the backport label Jan 29, 2025
@mergify mergify bot requested a review from a team as a code owner January 29, 2025 14:44
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 merged commit 7fd894e into 8.x Jan 29, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant