pulp / pulp/pulpcore

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

Open
#7,237 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Question
Dominant language
Python
Stars
598
Forks
168
Avg merge
1d 4h
Merged PRs (30d)
86

Description

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?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are identified in the issue. Start by locating Pulp Container deployment and load-handling documentation, then determine whether single-endpoint multi-instance deployments are supported, what constraints and reference architectures apply, and whether the documentation answers the roadmap question.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.