stackabletech / stackabletech/listener-operator
OpenShift Route backend
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 9
- Forks
- 2
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 8
Description
OpenShift provides the Route CRD, which allows OpenShift to automatically allocate public hostnames for services and provides load balancing and a convention for DNS configuration.
We could integrate by:
- Creating a
serviceTypethat creates Route objects - Setting the Listener's addresses to
Route.status.ingress[].host, but only ifingress[].conditions[type=Admitted].status=True(to prevent impersonation attempts)
Contributor guide
No contributing guide indexed for this repository
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
Read the OpenShift Route CRD documentation first, then locate the existing serviceType integrations and Listener address handling. Done means creating Route objects and using a Route status host only when its Admitted condition is true; no repository files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100