Project

Profile

Help

Story #5136

Story #5132: [Epic] As a user, I can consume Pulp 3 from OperatorHub.io

pulp-operator needs a stable & configurable accessible port

Added by mdepaulo@redhat.com 8 months ago. Updated 3 months ago.

Status:
NEW
Priority:
Normal
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

40%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
No
Sprint Candidate:
No
Tags:
CI/CD
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

Description

pulp-operator needs a stable & configurable port for pulp-content to be accessed on. Preferably for pulp-api as well.

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, the port is randomized.

Implementing this may involve implementing nginx. However, Kubernetes may provide the functionality of nginx that we use it for.

Associated revisions

Revision da436554 View on GitHub
Added by Mike DePaulo 7 months ago

Use actual ports 24816 & 24817 as nodePorts

Partially implements: ref #5136 https://pulp.plan.io/issues/5136

History

#1 Updated by mdepaulo@redhat.com 7 months 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.

#2 Updated by fabricio.aguiar 3 months ago

  • Tags CI/CD added

Please register to edit this issue

Also available in: Atom PDF