Is the pulp-ui supposed to be deployed by the operator ?
Open
Nobody has claimed this yet.
Feature
- Dominant language
- Go
- Stars
- 88
- Forks
- 66
- Avg merge
- 53m
- Merged PRs (30d)
- 1
Description
Hello, when I deploy pulp with a custom deployment (see : deploy-custom.txt), I now get the ui as a bonus.
When I use the operator (see : deploy-operator_instance.txt) , I don't get it.
Is the pulp-ui supposed to be deployed by the operator today ? Or in the future ?
Let me know, thanks.
Louis
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 comparing the attached deploy-custom.txt and deploy-operator_instance.txt deployment descriptions, then trace how the operator handles the Pulp UI deployment. Verify whether the operator is expected to provide pulp-ui and document the current behavior or the required change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100