Skip to content

Update fleet-agent-proxy-package-registry.asciidoc #1722

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Mar 6, 2025
Merged

Update fleet-agent-proxy-package-registry.asciidoc #1722

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f660088
Update fleet-agent-proxy-package-registry.asciidoc
lucabelluccini Mar 6, 2025
cc986e0
Update docs/en/ingest-management/fleet-agent-proxy-package-registry.a…
kilfoyle Mar 6, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/en/ingest-management/fleet-agent-proxy-package-registry.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,10 @@ example:
xpack.fleet.registryProxyUrl: your-nat-gateway.corp.net
----

If your HTTP Proxy requires authentication, you can include the
credentials in the URI, such as `https://username:[email protected]`,
only when using HTTPS.

== What information is sent to the {package-registry}?

In production environments, {kib}, through the {fleet} plugin, is the only service interacting with the {package-registry}. Communication happens when interacting with the Integrations UI, and when upgrading {kib}. The shared information is about discovery of Elastic packages and their available versions. In general, the only deployment-specific data that is shared is the {kib} version.
Loading