stackabletech / stackabletech/listener-operator
Derive load balancer IP from manually provisioned certificates
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 9
- Forks
- 2
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 8
Description
(For other SBLE staff, see https://stackable.atlassian.net/browse/SUP-187)
Currently, we support nudging NodePort services onto Nodes that have certificates provisioned, but we don't support anything similar for LoadBalancer services. That can make them difficult to use for short-lived listeners (like Kafka broker (non-bootstrap) listeners) if you require manually provisioned certificates.
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
Start by tracing how the listener-operator currently nudges NodePort services onto nodes with manually provisioned certificates, then compare that path with LoadBalancer services. Done means LoadBalancer services can derive their IP from appropriately certificated nodes, including short-lived listeners such as non-bootstrap Kafka broker listeners.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100