AppRecs review analysis
AppRecs rating 4.5. Trustworthiness 63 out of 100. Review manipulation risk 23 out of 100. Based on a review sample analyzed.
★★★★☆
4.5
AppRecs Rating
Ratings breakdown
5 star
92%
4 star
4%
3 star
4%
2 star
0%
1 star
0%
What to know
✓
Low review manipulation risk
23% review manipulation risk
✓
High user satisfaction
92% of sampled ratings are 5 stars
About kubenav - Kubernetes Dashboard
- Available mobile: kubenav provides the same experience as kubectl for mobile.
- Manage Resources: All major resources like Deployments, StatefulSets, DaemonSets, Pods, etc. are supported.
- Custom Resource Definitions: View all Custom Resource Definitions and mange Custom Resources.
- Modify Resources: Edit and delete all available resources or scale your Deployments, StatefulSets, DaemonSets.
- Filter and Search: Filter the resources by Namespace and find them by their name.
- Status Information: Fast overview of the status of workloads and detailed information including Events.
- Resource Usage: View the requests, limits and current usage of Pods and Containers.
- Logs: View the logs of a container or stream the logs in realtime.
- Terminal: Get a shell into a container, right from your phone.
- Manage multiple Clusters: Add multiple clusters via `kubeconfig` or your preferred Cloud Provider, including Google, AWS and Azure.
- Port-Forwarding: Create a port-forwarding connection to one of your Pods and open the served page in your browser.
- Prometheus Integration: kubenav allows you to view your Prometheus metrics directly in the dashboard and to build your own dashboards via the Prometheus plugin.
kubenav - Kubernetes Dashboard Screenshots
Tap to Rate:
Reviews for kubenav - Kubernetes Dashboard
Tom G Denver
Namespace nav is difficult and unintuitive
I would give this 5 stars, except navigating namespaces is unintuitive and difficult. Why can’t one just select a current namespace to work in? Go to settings > Namespaces and the list is empty — what?!? Then go to a resource, tap the little settings icon in the top right, then there is a filter for namespaces that lists all namespaces, so the app knows about them. But having to do this per resource and figure out where to do it, and the fact the Namespaces in settings requires manual entry of all namespaces when the app clearly can access the list, is totally ridiculous. Seems a basic feature is missing.
dystopiandev
I appreciate it
This saved loads of pain. Thanks