[RFE] Configure `routes` to `pulp-certguard`
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 88
- Forks
- 66
- Avg merge
- 53m
- Merged PRs (30d)
- 1
Description
Is your feature request related to a problem? Please describe.
We need to verify if our configuration of OCP Routes works with pulp-certguard.
The current configuration is already doing the edge TLS termination (the Ingress Controller terminates TLS encryption before forwarding traffic to pulp-api/pulp-content), but we also need to check if it is possible to do the missing configurations from https://docs.pulpproject.org/pulp_certguard/reverse_proxy_config.html.
Describe the solution you'd like
Verify if it is possible to configure OCP Routes with the settings from https://docs.pulpproject.org/pulp_certguard/reverse_proxy_config.html and, if it is, update the operator with the expected configs.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked pulp-certguard reverse proxy configuration documentation and compare its requirements with the current OCP Routes setup for pulp-api and pulp-content. Verify whether those settings can be represented by the operator, then update the operator with the expected configuration if supported. Done means the compatibility is established and the required operator configuration is documented or implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100