helm-dashboard VS kdash

Helm Dashboard is an open-source project by Komodor that offers a visual and user-friendly way to manage and visualize all the Helm charts installed in your clusters. Instead of using the terminal, you can leverage the Helm Dashboard's intuitive UI to perform a variety of tasks that make working with Helm a breeze. Here are some of its key features:

https://github.com/komodorio/helm-dashboard seems interesting, but a bit overkill for the dev/PM usecases compared to the DevOps folks using it.

Helm dashboard (https://github.com/komodorio/helm-dashboard/) is my first big open-source project, and during the last couple of months, we at Komodor have consistently been working on improving it (We released a GA and got 3K stars in a couple of months), but we were scratching our heads with the future roadmap!

Helm dashboard (https://github.com/komodorio/helm-dashboard) is my first big open-source project, and during the last couple of months, we at Komodor have consistently been working on improving it (We released a GA and got 3K stars in a couple of months), but we were scratching our heads with the future roadmap!

The tricky part of OSS is that it's hard to know what should be developed next; we tried a couple of methods to make this work:

Helm Dashboard

As always, we welcome everyone to provide feedback and suggestions on the project’s roadmap on our social channels, GitHub, or the Slack Kommunity. We’ve even created a user survey form to make it easier on you 🙂

Regardless, if you're also using (suffering) from Helm, we have a cool open source GUI to help with that: https://github.com/komodorio/helm-dashboard

Check it out on GitHub: https://github.com/komodorio/helm-dashboard

A simple terminal dashboard for Kubernetes built with Rust, best alternative k9s

kdash: A fast and simple dashboard for Kubernetes. Its created by me :)

[Optional] KDash

Note: I'm using KDash to monitor the cluster; you can try it or use kubectl, k9s, and so on as you prefer.

When you communicate with a Kubernetes cluster, using kubectl, or a client library, or a tool like KDash, you are primarily interacting with the Kubernetes API server. The API server is responsible for managing the cluster and is responsible for handling requests from a client.

Mostly KDash and if possible progress on a JHipster blueprint for Rust microservices

I'm not building web-apps yet, currently i'm doing a terminal UI app. You can check the cargo.toml for deps. I'm planning to build a Rust blueprint for JHipster quite soon so I'll be able to directly compare productivity with Spring boot. And yes there is no equivalent of SB in Rust but I don't think you need that in Rust, there are great web frameworks like Actix or Rocket which provides most of what you need from SB and since you dont have to do OOP in Rust you actually dont need many Hibernate like features IMO, but you have http://diesel.rs/ to cover that.