stackabletech / stackabletech/listener-operator
Correlate Listener to Stacklet/indirect owner
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 9
- Forks
- 2
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 8
Description
This is required for product operators to be able to watch Listeners properly (primarily to generate discovery config). It's theoretically possible to reproduce by following the path (using ownerReferences if nothing else is specified) Listener -> PersistentVolume -> PersistentVolumeClaim (via PV.spec.claimRef) -> Pod (by.. iterating over them and looking for the matching claim mount? ew) -> StatefulSet -> Stacklet.
Another approach would be to use our conventional labels on the PVC (app.kubernetes.io/{name,instance,component}), but that isn't really scoped to Stackable (as opposed to any other way to run HDFS). Then again, that's arguably "fine" if we end up doing spurious reconciles once in a while...
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 Listener ownership is currently resolved and investigate the proposed Kubernetes path from Listener through PersistentVolume, PersistentVolumeClaim, Pod, and StatefulSet to Stacklet, including PV.spec.claimRef and ownerReferences. Compare that with the conventional PVC labels approach; done means operators can reliably correlate a Listener with its indirect owner for discovery configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, python
- Domain
- infrastructure, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100