Story #5136
Updated by mdepaulo@redhat.com about 3 years ago
pulp-operator needs a stable & configurable port for the pulp webserver (nginx/apache) 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, pulp-api and pulp-content are exposed directly without the webserver, and the port is randomized. Implementing this may involve implementing nginx. However, Kubernetes may provide the functionality of nginx that we use it for.
.