Running Multiple Pulp Container Instances Behind a Single Endpoint for Load Handling

[VrindaMarwah]

Is it officially supported to run multiple Pulp Container instances behind a single endpoint to handle higher pull/load traffic?

If yes:

• Are there any specific requirements or constraints to support this?
• Are there any recommended/supported reference architectures for this setup?
• Any documentation available for the same

If not:

• Is it on the Pulp roadmap and will be available as a feature in future?

[gerrod3]

@VrindaMarwah It depends on exactly what you want, do you want multiple Pulp instances each with their own separate database and storage? Or do you want multiple API/Content/Task workers to handle more work? If I'm correct and you want the latter, then I would recommend using podman/docker compose:
https://pulpproject.org/pulp-oci-images/docs/admin/tutorials/quickstart/#podman-or-docker-compose

With compose each process gets their own image and thus can be scaled up/down to the size you want. You can also migrate from an existing single-container instance by using the folders compose file. The biggest constraint is the hardware available on your machine.

If you need even more scaling then you'll probably need to look into the operator: https://pulpproject.org/pulp-operator/