kubevious VS komoplane

Unlike the other tools mentioned in this post, Kubevious has no way of changing the cluster state. It is intended solely as an observability tool, focusing on potential issues in your cluster. It highlights potential threats and risks for every resource you may run.

kubevious: UI tool and query the cluster with regex https://github.com/kubevious/kubevious

Project: Kubevious

In many ways, Kubevious is like many other Kubernetes Dashboard alternatives in that it provides the capability to view, edit, and maintain your configurations. However, Kubevious is going strong on one specific selling point: simplicity.

But since you asked I’ll give quick summary to the scope of the change. Prior version of Kubevious comes with a graphival view, where resources are reresented in a tree structure under namespaces and grouped in a logical group of “application”. This lets you see configmaps, services, ingresses, etc that are somehow related to this application. See here: https://github.com/kubevious/kubevious

To try out Komoplane, head over to: https://github.com/komodorio/komoplane. You can install it via a Helm chart, or you can just run it as standalone binary on your laptop. Don't forget to give it a star if you liked it ;)

Your feedback and insights are crucial in shaping the project’s roadmap and making it even more valuable to Crossplane users. As an open-source project, we welcome contributions, suggestions, and bug reports from devs and platform engineers alike. Feel free to share your feedback with us via GitHub Issues or our Slack Kommunity (#komoplane).