RequestHunt is a community-driven platform that collects and curates feature requests from X (Twitter), Reddit, and GitHub. We help product teams discover what features real users are asking for, making it easier to validate product ideas and prioritize feature development based on actual user demand.

How does RequestHunt collect feature requests?

RequestHunt uses AI-powered extraction to automatically collect feature requests from social media platforms including X, Reddit, and GitHub. The platform monitors discussions, issues, and posts to identify genuine user feature requests, extracting key information like the requested feature, product mentioned, and user sentiment.

Who uses RequestHunt?

RequestHunt is used by product managers, founders, developers, and product teams who want to discover what features real users are requesting. It's particularly valuable for startups looking to validate ideas, established companies prioritizing their roadmap, and developers building products that solve real user problems.

Is RequestHunt free to use?

Yes, browsing and searching feature requests on RequestHunt is completely free. We also offer API access for developers who want to integrate feature request data into their own applications. Check our pricing page for API plan details.

How often is RequestHunt data updated?

RequestHunt continuously collects feature requests from Reddit, X (Twitter), GitHub, YouTube, LinkedIn, and Amazon. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[KServe] Support per-LLMInferenceService resource overrides for storage initializer container

Extend the Go API to allow specifying a template for the initcontainer with the name `constants.StorageInitializerContainerName` for `LLMInferenceService`, as the current cluster-global `ClusterStorageContainer` is not suitable.

Original Source

@@fenollp | 1 pts | 3/11/2026

/kind feature **Describe the solution you'd like** cc #5162 I would like to extend this request to the more recent `LLMInferenceService` as well. To us, a cluster-global `ClusterStorageContainer` is not a correct solution. We would like an extension of the Go API to be able to specify a template of the initcontainer with the name `constants.StorageInitializerContainerName`. Today (v0.16.1), the type `kservev1alpha1.LLMInferenceServiceSpec` has a field `Template` of type `corev1.PodSpec` which allows setting `.Containers` (and `.Resources` and `.SecurityContext` and others). However the `.InitContainers` field is not merged in a "smart enough way". Meaning that setting an initcontainer with the storage-initializer name there ends up trying to create 2 initcontainers with the same names: the one I add plus the one from kserve. This is asking to merge these two initcontainers when both are provided (same name). This would allow setting the initcontainer's Resources as well as Envs a

Discussion

Loading comments...