Not all Elastic Stack setups have access to the internet. For the Ingest Manager to fully function, access to https://epr.elastic.co is required. To work around this, it is possible to modify the URL to which Kibana connects. This can be done through xpack.fleet.registryUrl: 'http://localhost:8080'. Today this mainly used for the development of the package registry and testing of new packages before they are released.

IMPORTANT: This config should not be used by users yet and is not supported!

With the above config, it is is possible to run a registry on prem. The package registry with packages is available as docker container under docker.elastic.co/package-registry/distribution:production for production. This is currently compatible with 7.10.0 deployment of Kibana. To run this registry locally, the following command can be used: docker run -p 8080:8080 docker.elastic.co/package-registry/distribution:production

Even though all of the above is possible today, it is not supported and for development only. This issue is to discuss further on what the open issues are to make it supported and how to solve them.

Issues that are still open:

• As long as epr.elastic.co is used, we can guarantee the registry is always the newest version. As soon as it is run on prem, Kibana must enforce a minimal version of the registry to properly work. What is our compatibility matrix?
• What is the recommended upgrade scenario for on prem registry users? How often will these users need / get updates for the packages?
• What version do we recommend on prem users to use?
• What is our recommended way of running the registry?