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.

[Kubernetes] Add support for managing VyOS Router VMs via QEMU Guest Agent

A user has developed an operator to manage VyOS Router VMs from Kubernetes without needing SSH access, utilizing QEMU Guest Agent instead. They are looking for feedback on this approach and its adoption in network automation.

Original Source

@u/tjjh89017 | 13 pts | 3/13/2026

I run VyOS as routers in both KubeVirt (on Harvester) and Proxmox VE. Got tired of SSHing into each VM to push config. Ansible doesn't really help either, it still depends on management network and SSH being reachable, which is exactly the thing your router is supposed to provide. So I wrote an operator that does it through QEMU Guest Agent instead. No SSH, no network access to the router needed. You write VyOS config as CRDs — `VRouterTemplate` holds config snippets with Go templates, `VRouterTarget` points to a VM, and `VRouterBinding` ties them together. The operator renders everything and pushes it via QGA. If the VM reboots or migrates, it detects and re-applies. Two providers so far: - KubeVirt (tested on Harvester HCI v1.7.1) - Proxmox VE (tested on PVE 9.1.6) Built with Kubebuilder. Provider interface is pluggable so adding new hypervisors shouldn't be hard. GitHub: https://github.com/tjjh89017/vrouter-operator Anyone else doing network automation with VMs in K8s? Curious how others handle this. Update with Demo Video in Youtube, hope this can help you to understand more. https://www.youtube.com/watch?v=RsieH9gFU4I

Discussion

Loading comments...