Story #5136
closed
Story #5132: [Epic] As a user, I can consume Pulp 3 from OperatorHub.io
pulp-operator needs a stable & configurable accessible port
40%
Description
h1. !! Ticket moved to GitHub: "pulp/pulp-operator/257":https://github.com/pulp/pulp-operator/issues/257
pulp-operator needs a stable & configurable port for the pulp webserver (nginx/apache) to be accessed on.
This way, sysadmins can say update DNS records for their pulp server to redirect clients to a new Pulp server, without changing the client config on every single system.
Currently, pulp-api and pulp-content are exposed directly without the webserver, and the port is randomized.
Updated by mdepaulo@redhat.com almost 5 years ago
- % Done changed from 0 to 40
As part of implementing https://pulp.plan.io/issues/5061 on the k3s branch, I started on this.
The 2 ports (content and api) are stable, but not configurable. They are both 24816 & 24817.
Added by Mike DePaulo almost 5 years ago
Updated by fao89 almost 4 years ago
- Category set to Operator - Moved to Github Issues
Updated by mdepaulo@redhat.com about 3 years ago
- Assignee deleted (
mdepaulo@redhat.com)
Updated by fao89 over 2 years ago
- Description updated (diff)
- Status changed from NEW to CLOSED - DUPLICATE
.
Use actual ports 24816 & 24817 as nodePorts
Partially implements: ref #5136 https://pulp.plan.io/issues/5136