stackabletech / stackabletech/nifi-operator
Better Nifi cluster status api
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 48
- Forks
- 12
- Avg merge
- 11h 26m
- Merged PRs (30d)
- 10
Description
Issue checklist
We now have a ClusterIP service called <nifi-cluster-name>-reporting-task that always points to a single Nifi pod in the StatefulSet. This is used to query the Nifi cluster status and ensures that the Nifi JWT token can be validated by the same pod that generated it.
This was implemented here and was more of a quick workaround.
What we should have:
- a better name for the service. Proposal:
<nifi-cluster-name>-cluster-status. - this service should be configurable as
externalso that clients outside the K8S cluster can query it too. The getting started guide would need it. - optional: maybe a more robust routing in case the said pod becomes unavailable. This very much depends on Nifi's implementation of authorization.
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 reviewing the implementation referenced in pull request 571 and trace how the current ClusterIP service is defined. Done should include the proposed service name, external configurability, and the corresponding getting started guide update; robust routing is optional and depends on NiFi authorization behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- api, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100